Compliance
Compliance overview
Updated 2026-10-08
Two design goals: raw card data should never touch your business, and no single processor should be able to stop your checkout. Everything below follows from those two.
Tokenization at capture
When a customer enters a card, it is tokenized at the point of capture. Your checkout, your CRM and your subscription logic only ever handle the token. The card number is not stored on, transmitted through, or visible to your systems, which keeps your own PCI DSS obligations small.
A vault under your name
Tokens, customer profiles and subscription schedules are held in a vault that is yours. Processors connect to the vault to run transactions; the vault does not belong to any one of them. Adding or replacing a processor is a routing change, your data can be exported at any time in a documented format, and a processor relationship ending does not end your ability to bill.
Transaction screening
Transactions are screened for fraud before they are routed, with rules tuned to your business rather than a generic default. 3-D Secure 2, the card networks' step-up verification, is available on your account and can be applied by rule, for example above a ticket size or for specific regions.
Routing, retries and redundancy
With more than one merchant account behind the vault, transactions are routed by card type, region, amount and recent processor performance. A soft decline (one the issuer would approve on a retry) can retry through an alternative route where the card network rules allow it. Routing decisions are visible in your dashboard.
Reserves and settlement
Settlement lands two business days after the transaction. If underwriting sets a reserve, it comes with a stated release schedule, written into your offer before you sign, and reviewed as your history builds. Reserves do not appear after the fact.
What you receive at onboarding
Compliance documentation for the vault and the processing infrastructure is provided during onboarding, together with the merchant agreement, the fee schedule and any reserve terms. If your own compliance, bank or auditor needs something specific, ask your named contact and we will source it before you sign.
What we do not do
- We do not collect card or bank details on this website. The application form asks for your business basics and contact details only.
- We do not run analytics or third-party scripts on this website.
- We do not onboard businesses or products the card network rules prohibit, or businesses that cannot pass identity and business verification.
- We do not sell or share your application data. It goes to the processors we take your application to, and nowhere else.