Frequently asked questions

Settlement timing depends on the corridor and the rail. Card acquiring settles on a rolling T+2 basis for domestic US and EU transactions. ACH debits clear in one to two business days, SEPA credit transfers in one business day, and wire payouts are usually same day when instructed before 15:00 ET. Emerging market corridors such as Brazil and Indonesia can take five to nine business days because of local clearing windows and exchange controls. Every account receives a published settlement calendar per corridor, and the daily reconciliation file shows which batch each payment landed in. Corridor level detail is documented in Payment Processing.

We settle in USD, EUR, GBP, JPY, SGD, AUD, CAD and more than twenty additional currencies, with automatic conversion at interbank adjacent rates and a disclosed markup per pair. On the collection side we support Visa, Mastercard and Amex acquiring, ACH and wire in the United States, SEPA and bank redirect methods in Europe, and local rails including PIX in Brazil, UPI in India, PayNow in Singapore and iDEAL in the Netherlands where an acquiring relationship exists. Method availability is confirmed per market during onboarding rather than advertised globally, because licensing and scheme rules differ by jurisdiction.

Every transaction is written to a double entry ledger with a unique batch identifier, so a payment can be traced from authorization through clearing, conversion and payout. A reconciliation file is generated each business day in CSV and through the API, matching settled amounts against your orders line by line; unmatched items are flagged with a reason code rather than silently dropped. Standard reporting covers gross volume, net settlement, fees, refunds, chargebacks and foreign exchange variance by entity, currency and corridor. Finance teams using these exports typically close the month in two to three days.

Card disputes arrive through the acquiring bank and reach you as a webhook within minutes, carrying the reason code, the disputed amount and the response deadline. Our risk team assembles the evidence package: order details, delivery or access confirmation, prior correspondence, IP and device fingerprints, and the 3-D Secure authentication result where one exists. You review and approve the submission, we file it with the issuer and track the representment through to the outcome. Customer credit and refund rules are documented in Refund Policy, and a dispute ratio above 1 percent triggers a review of the affected corridor.

For a market where we already hold acquiring relationships and a local banking partner the typical path is six to ten weeks: two weeks for regulatory and tax assessment, two to three weeks for the entity or registration decision, two weeks for bank account opening and KYB, and one to two weeks for integration and test transactions. Markets that require a local license, a resident director or in person bank verification run three to six months. We publish a week by week plan with named owners before any work starts, and the assessment phase is not invoiced until you approve that plan.

We coordinate the work but do not act as a law firm or as the corporate services provider of record. In practice we prepare the incorporation pack, engage vetted local counsel and registered agents, arrange tax and VAT registration, open the bank accounts and register the entity with the relevant payment schemes. You remain the owner and signatory of every entity; we hold delegated operational access only. Where a full entity is disproportionate we also structure merchant of record or branch arrangements so that you can collect locally without incorporating. Entity structures are revisited annually against volume and regulatory change.

Local methods are added per market rather than switched on globally. We first confirm which rails actually carry volume for your category using our own corridor data, then integrate the acquirer or scheme with the best authorization and cost profile. Wallet and bank redirect methods are exposed through the same API as card payments, so your checkout calls one endpoint and we route based on the country and currency of the buyer. Where a method requires a local entity or a specific merchant category code we tell you before integration begins, not after. Routing rules remain configurable per market.

We operate SOC 2 controls covering security, availability and confidentiality, and card operations run under PCI DSS controls. The independent attestation audits for both are in progress and we do not yet hold a completed report. Client facing control documentation is available under a non disclosure agreement. We also operate under GDPR and CCPA obligations with a documented data processing agreement, a records of processing register and annual penetration testing by an independent firm. Where a client needs a specific control evidenced, our compliance team supplies the policy and the audit artifact rather than a generic assurance letter. Scope is described in Compliance & Risk.

For the business we need the certificate of incorporation or equivalent registration, the registered address, a register of directors, and identification for every beneficial owner holding 25 percent or more. For each of those individuals: a government issued photo ID, proof of residential address dated within three months, and nationality and tax residency details. We also ask for a short description of expected monthly volume, the corridors involved, average ticket size and refund rates, plus your website and terms of sale. Most clients complete this in three to five business days; regulated or multi entity structures can take two to three weeks.

Production data resides in us-east-1 for payments and settlement, eu-west-1 for compliance and data residency workloads, and ap-southeast-1 for APAC expansion and payouts, each with a named failover region. Cardholder data never reaches the analytics environment; it is tokenized at the point of capture and only tokens are stored. Personal data of EU and UK residents stays in region unless a transfer is operationally necessary, in which case it moves under Standard Contractual Clauses with a documented transfer impact assessment. Sub processors, their locations and their purposes are listed in Privacy Policy and updated whenever they change.

Incidents are classified by severity and routed to a named client contact and to the shared operations channel. For anything affecting availability or data confidentiality we notify affected clients within 24 hours of confirmed impact, stating what happened, which systems and data were involved, the containment action already taken and the time of the next update. Regulatory notifications, including the 72 hour requirement under GDPR, are prepared by our compliance team and filed by the controller where the obligation sits with you. A written post incident review follows within five business days and corrective actions are tracked to closure at the quarterly business review.

Yes. The platform is API first: REST over HTTPS with JSON request and response bodies, idempotency keys on every write operation, cursor based pagination, and predictable error objects carrying a machine readable code and a human readable message. Reference documentation covers payments, payouts, refunds, disputes, reconciliation exports and account configuration, with runnable examples in cURL, Python, Node and PHP. Versioned endpoints are additive; breaking changes are released under a new version with at least 90 days of notice. Client API keys are scoped per environment and per entity and can be rotated from the dashboard without downtime.

A hosted checkout integration, where we render the payment page and you send the buyer to it, is usually live in five to ten business days including test transactions. A direct API integration with your own checkout, webhook handling and reconciliation export typically takes three to five weeks depending on your release cycle. Multi entity or multi currency setups with custom routing rules run six to eight weeks. Most of the elapsed time in these projects is spent on QA and release windows on your side rather than on our build, which is why we schedule a joint test window at kickoff.

Yes. Webhooks fire on payment authorized, captured, failed and refunded, on disputes opened and resolved, and on payouts scheduled and settled, plus a reconciliation file ready event. Each delivery is signed with an HMAC SHA-256 header so you can verify that the payload came from us, and it carries a delivery identifier for deduplication. Failed deliveries retry on an exponential backoff schedule for up to 72 hours, and every attempt is visible in the dashboard log so an event can be replayed manually. We recommend treating webhooks as notifications and the API or the daily reconciliation file as the source of truth for balances.

Every account gets a sandbox with its own API keys, test card numbers that produce deterministic outcomes for success, decline, insufficient funds, 3-D Secure challenge and fraud flags, and simulated settlement and payout cycles that can be advanced on demand. Sandbox data is isolated from production and purged every 90 days. Webhooks, reconciliation exports and dispute flows behave the same as they do in production, so integration tests do not need rewriting before go live. Moving to production requires a completed checklist review with our integration team, which usually takes one to two business days.

Pricing has three components. A one time setup fee covers KYB, entity and corridor configuration and integration support; it is quoted after the scoping call and is typically between $2,500 and $10,000 depending on the number of entities and markets. A monthly platform fee covers the account, monitoring, reporting and support, and it scales with the number of active corridors. Transaction costs are passed through at the corridor rate plus a disclosed percentage, so you can see what the acquirer charged and what we added. We do not charge for failed authorizations or for sandbox usage.

Standard agreements run twelve months with 60 days termination notice, and there is no minimum monthly volume for the first two quarters while you ramp. After that a minimum platform fee applies, waived in any month where processed volume exceeds the agreed threshold. Monthly rolling terms are available to clients with more than twelve months of history. Exit is designed to be clean: we provide a full transaction and reconciliation export, transfer or close the acquiring relationships at your instruction, and return all credentials within ten business days of the effective date.

Five stages, usually four to six weeks end to end. Stage one is a scoping call where we map your markets, methods, entities and volume. Stage two is commercial and compliance: the quote, the agreement and KYB document collection. Stage three is technical configuration, corridor setup and sandbox integration. Stage four is a joint test window covering the success, decline, refund, dispute and reconciliation paths with your finance team. Stage five is production go live with a named operations contact, a daily check in for thirty days and a formal review at day ninety. Nothing is invoiced until the first production settlement completes.