Cardflo
BETTER APPROVAL RATES
cardflo.io
Cardflo · Smarter Payments Built Around You
01 / 12

Give valid payments
a stronger first attempt.

Cardflo is your payments partner for enriched authorisation data, merchant account matching and routing shaped by issuer responses.

TransactionROUTING
Matched payment routes
Primary partner
Matched
Backup partner
Ready
Cascade route
On decline
One connection50+ partners
The payment problem
Cardflo
BETTER APPROVAL RATES
cardflo.io
Cardflo · Smarter Payments Built Around You
02 / 12

Legitimate purchases fail when payment data does not explain the transaction.

1Incomplete billing data

Missing or contradictory address fields leave issuers with less reliable purchase context.

2Stale saved credentials

Expired or replaced cards disrupt returning customer purchases and subscription collections.

3Wrong payment flags

Stored credential and recurring indicators fail to distinguish checkout purchases from renewals.

4Exemptions without fallback

An issuer requests authentication, but checkout cannot move the customer into a 3DS2 flow.

5Unsuitable partner routes

A route lacks support for the token format, currency or authentication data being submitted.

6Misdiagnosed declines

Fraud blocks and insufficient funds are treated as gateway faults, triggering futile retries.

Why it matters
Cardflo
BETTER APPROVAL RATES
cardflo.io
Cardflo · Smarter Payments Built Around You
03 / 12

Improve the first request before adding another attempt.

Cardflo connects checkout context with acquirer partner capabilities. Align tokens, billing fields and authentication rules, then measure comparable issuer segments rather than headline averages.

Richer payment context

Map supported billing and transaction fields consistently across partner payloads.

Current token credentials

Support network tokens and lifecycle updates where partner capabilities allow.

Eligible exemption requests

Apply documented eligibility rules and retain authentication fallback.

Correct credential flags

Distinguish customer purchases from merchant-initiated subscription collections.

Accurate MCC alignment

Match the MCC to actual trading activity, not a desired approval outcome.

Comparable performance

Assess first-attempt acceptance by issuer, market, token type and authentication path.

How it works
Cardflo
BETTER APPROVAL RATES
cardflo.io
Cardflo · Smarter Payments Built Around You
04 / 12

Turn checkout context into a complete, supported authorisation request.

Purchase contextBasket and billingCredential contextToken and payment flagsAuthentication3DS2 and eligibilityCARDFLOEligibility · Orchestration · ControlValidate data and select eligible routeToken-ready partnerSupported cryptogramsAuthenticated route3DS2 data preservedExemption requestIssuer decision appliesSupport varies by acquirer partner and market. Issuers decide whether to approve or require authentication.
Platform overview
Cardflo
BETTER APPROVAL RATES
cardflo.io
Cardflo · Smarter Payments Built Around You
05 / 12

One orchestration layer for the details that influence acceptance.

One platform
8
relevant controls
Network tokens
Support current token credentials.
Payload mapping
Align supported ISO 8583 fields.
Credential flags
Identify saved card and renewal payments.
Exemption rules
Request only eligible exemptions.
3DS2 fallback
Handle issuer authentication requests.
Partner routing
Match market and payload capabilities.
Controlled cascading
Respect response codes and retry rules.
Acceptance reporting
Compare like-for-like issuer segments.
A payment, recovered
Cardflo
BETTER APPROVAL RATES
cardflo.io
Cardflo · Smarter Payments Built Around You
06 / 12

Recover eligible payments without repeating the same mistake.

Authenticate when requested
An authentication-required response calls for 3DS2, not a blind switch of partner.
Cascade only when eligible
Use another approved route only when response codes and scheme rules permit.
Stop prohibited retries
Do not use routing to evade fraud blocks, merchant restrictions or stop instructions.
Transaction journey
01Returning customer pays for an eCommerce order
02Choose a partner supporting the token and market
03Issuer requests authentication after an exemption
04Eligible cascade to the next route
05Complete 3DS2 and resubmit where permitted
Routing with context
Cardflo
BETTER APPROVAL RATES
cardflo.io
Cardflo · Smarter Payments Built Around You
07 / 12

Supported network token: route with context.

Payment signalRouting responseCommercial reason
Supported network tokenChoose token-capable partnerPreserve credential and cryptogram
Exemption rejected, 3DS2 requiredAuthenticate before resubmissionMeet issuer authentication demand
Eligible technical failureCheck status before alternate routeAvoid duplicate authorisations
Hard decline or stop instructionStop automated cascadingRespect issuer and scheme rules
Underwriting readiness
Cardflo
BETTER APPROVAL RATES
cardflo.io
Cardflo · Smarter Payments Built Around You
08 / 12

Show whether the acceptance gap is technical, financial or risk related.

Six months of authorisation logs by issuer and response code

Token type, payment method and authentication breakdowns

ISO field mappings and stored credential specifications

3DS2 policies, exemption rules and fallback test records

Token requestor, cryptogram and lifecycle evidence by market

Typical merchant category codes
ReviewAssigned during underwriting
Prepared around your model, markets and controls.
Onboarding flow
Cardflo
BETTER APPROVAL RATES
cardflo.io
Cardflo · Smarter Payments Built Around You
09 / 12

Start with decline evidence, then match and validate the route.

01
Map
Business model and markets
02
Evidence
Review logs and data controls
03
Match
Match partner capabilities
04
Integrate
Checkout, API or plugin
05
Validate
Test rules and descriptors
06
Optimise
Monitor routes and disputes
Whole of market
Cardflo
BETTER APPROVAL RATES
cardflo.io
Cardflo · Smarter Payments Built Around You
10 / 12

Match merchant accounts to the business and its payment data.

Cardflo helps match merchants with acquirer partners by actual activity, MCC, markets and billing model, then checks support for tokens, authentication and enriched payloads.

Your business
Merchant profile
Trading activityActual inventory and accurate MCC
Payment modeleCommerce checkout or subscriptions
Issuer mixCountries, currencies and card types
Control evidenceField tests, token logs and 3DS2 policies
Token-capable account
Supports the merchant model, token format and markets
Matched
3DS2-capable account
Supports authentication data and eligible exemptions
Matched
Unsupported payload route
Cannot carry required credential or authentication fields
No match
Commercial value
Cardflo
BETTER APPROVAL RATES
cardflo.io
Cardflo · Smarter Payments Built Around You
11 / 12

Make acceptance optimisation measurable, not speculative.

Acquirer partners
50+
Plus 400+ payment methods through one connection.
Stronger initial requests
Address missing fields before legitimate customers encounter avoidable declines.
Less needless friction
Request eligible exemptions while preserving a path to issuer-required authentication.
Healthier saved card flows
Support current tokens and correct indicators for returning buyers and subscriptions.
Cleaner performance evidence
Separate first-attempt approvals from recoveries and shifts in traffic mix.
More disciplined recovery
Avoid repeated submissions that cannot resolve credit, fraud or policy declines.
Better partner fit
Align merchant risk and technical needs before directing volume to a new account.
Cardflo
BETTER APPROVAL RATES
cardflo.io
Cardflo · Smarter Payments Built Around You
12 / 12

Build better approval rates on better payment evidence.

Share your issuer response analysis, integration mappings and authentication policies. Cardflo will help identify suitable acquirer partners and the configuration gaps worth addressing first.

Evidence-led acceptance reviewMerchant account and capability matchingControlled routing and recovery