AQ Pay

Built for the business modelsthat stress ordinary gateways.

Every sector transacts differently — ticket size, delivery timing, dispute exposure, methods and regulation. The platform is the same; the configuration is not. Here is how we think about each.

01 · E-commerce

E-commerce

Cross-border stores live or die on checkout conversion. The levers are local methods, local acquiring, sensible 3DS policy and clear declines customers can act on.

Routing by regionLocal methods3DS exemptions
RoutingLocal acquiring where it existsDomestic routes typically approve better and cost less; profiles route by issuer country automatically.
MethodsCountry-specific payment methodsBank redirects and wallets added per market with one status model.
RiskFrictionless 3DS where allowedExemption strategy for low-risk, low-value traffic; challenge where the score demands it.
OpsMulti-currency settlementPresent in local currency, settle in yours, see FX on every payment.
Merchant services
02 · Subscriptions

Subscription businesses

Recurring revenue is only as good as renewal success. Card lifecycle, retry timing and dunning determine involuntary churn — and issuers watch retry behaviour closely.

Smart retriesAccount updaterDunning
RetriesSchedules that respect decline codesInsufficient funds retries on payday patterns; hard declines are never retried.
CardsAccount updater & network tokensWhere schemes support it, expired or reissued cards keep working.
BillingPlans, trials, prorationBilling logic lives in the platform, not in your codebase.
RiskMerchant-initiated transaction flagsCorrect MIT/CIT framing keeps recurring payments exempt from repeated 3DS.
Subscription billing
03 · Digital

Digital products & services

Instant delivery leaves no time to review after authorization. Fraud has to be caught before the payment, and refunds have to be fast when it isn’t.

Pre-auth screeningVelocity rulesInstant refunds
RiskScreening before authorizationVelocity, device and behavioural signals stop card testing and bulk fraud at the gate.
RoutingGlobal reach from one integrationAdd regional providers as you expand, without touching the integration.
OpsDispute automationDelivery and access logs attached to representment automatically.
Risk & monitoring
04 · Travel

Travel & hospitality

High tickets, delayed delivery and multi-party fulfilment make travel a specialist acquiring category. Resilience across more than one acquirer is not optional.

Multi-acquirerDelayed deliveryDispute workflows
AcquiringSpecialist partnersIntroductions to acquirers that underwrite delayed-delivery models, subject to their approval.
RoutingExposure spread by designRoute by region and ticket size across acquirers; cascade on technical declines.
OpsLong dispute windowsDispute tooling built for cases that arrive months after booking.
FXMulti-currency settlementSettle in the currency of your supplier payments where possible.
High-risk & specialist acquiring
05 · Platforms

Marketplaces & embedded payments

Platforms need to onboard sellers, route their payments, report per seller and keep their own brand on everything. That is the white-label model applied to software.

Sub-merchant onboardingWhite-labelPer-seller reporting
OnboardingSub-merchants via API or portalCreate merchants, collect KYB data and assign profiles programmatically.
BrandYour checkout, your dashboardsSellers see your brand; AQ Pay stays invisible.
RoutingPer-seller profilesDifferent sellers, categories or regions can route differently.
FinanceReporting per sellerSettlement and fees broken down by sub-merchant for your payouts.
White-label gateway
06 · Regulated

Gaming & regulated industries

Licensed gaming, financial services and other regulated categories need specialist acquiring, strict screening and detailed reporting. Eligibility depends on licence, jurisdiction and partner appetite.

Eligibility-dependentEnhanced riskJurisdiction rules
EligibilityLicence and jurisdiction firstWe assess what you are licensed to sell, where, before any partner introduction.
RiskEnhanced screeningGeo-fencing, age and identity checks integrated into the pre-authorization pipeline.
AcquiringSpecialist partners onlyIntroductions limited to acquirers who serve the category; their decision is final.
ReportingRegulator-ready dataTransaction-level exports structured for compliance reporting.
How eligibility works

Don't see your sector? Describe it.

We configure per business, not per label. Tell us how you transact and we'll tell you what we'd set up — and what depends on partner approval.

Book a demo

Built for the business modelsthat stress ordinary gateways.

Every sector transacts differently — ticket size, delivery timing, dispute exposure, methods and regulation. The platform is the same; the configuration is not. Here is how we think about each.

{{ j.t }}
{{ i.n }}

{{ i.t }}

{{ i.d }}

{{ tg }}
{{ p.k }}{{ p.t }}{{ p.d }}
 {{ i.cta.t }}

Don't see your sector? Describe it.

We configure per business, not per label. Tell us how you transact and we'll tell you what we'd set up — and what depends on partner approval.

Book a demo