Current public status
Requires an eligible Stripe setup and successful payment-provider configuration.
Payment availability, settlement time, returns, and disputes are subject to the payment provider and payment method.
Aptoria is not a bank and does not hold customer funds.
Availability boundary
Published status
Limited availability
Provider or jurisdiction
Verify before use
Result
No outcome promise
Controls before use
Configuration, provider setup, and a reviewable record matter more than a feature-page promise.
Payment-provider receipts and payment status are retained with the related record.
High-impact money actions follow authorization and approval controls; failed or uncertain states are not treated as settled.
Control check
Source records
Reviewable
Policy
Configured by owner
Exception path
Human owner
When Aptoria pauses
Bank-detail changes, refunds, reversals, disputes, and reconciliation exceptions require an authorized human review.
Do not treat a draft, sample, or activity entry as proof of delivery, settlement, legal validity, or compliance.
Use the Trust Center and Availability pages for the current workflow boundary before enabling a customer-facing process.
Escalation
Sensitive or uncertain
Pause and review
Decision owner
Authorized human
Record
Keep evidence with workflow
Trust without theater
Verifiable, not vibes.
Three things you can check yourself — without a sales call, without a logo carousel.
See exactly how we measure it
Switching from another tool?
Review the workflow before relying on it.
Aptoria publishes availability, controls, and human boundaries instead of treating a feature page as a provider, legal, security, or outcome guarantee.