Docs
Payment methods and routing
You connect your own accounts. Cortana decides which one takes each payment, using rules you set.
Methods
- Card
- Stripe (in-page form) and Whop (hosted checkout). Connect as many accounts of each as you like.
- Crypto
- PayerURL, hosted checkout. Live mode only; it has no sandbox.
- Bank transfer
- Your own instructions. The payer uploads a receipt (PNG, JPEG, WebP or PDF up to 5 MB), you approve or reject it in Bank review. Approval is the only way it becomes paid.
Payments settle straight into your provider accounts. Cortana never holds funds, and keys are stored encrypted and never shown again.
How a card account is chosen
Each method has a routing strategy, set under Connections → Routing.
- Priority
- The first eligible account in your list. The next one only takes over when the first is capped, off or erroring.
- Weighted
- Payments are spread by weight, for example 60/40. A weight of 0 is standby: used only if every weighted account is unavailable.
Routing only ever uses accounts in your own workspace.
Caps and failover
Give an account a cap of a maximum amount, a maximum number of payments, or both, per day or per month (UTC). Paid and in-flight payments count. When a cap is reached the account is skipped until the period rolls over. If starting a payment fails on one account, Cortana tries the next, up to three, and records why on the payment (routing_reason).
Pinned payments finish where they started
Eligible means ready
An account takes new payments when it is on, its key validated, and its webhook verified. A key the provider rejects takes the account out of routing and emails your owners and admins once. Replacing the key brings it back.