Payment Processing & Acquiring · Use case

Accept online card payments

Scope this use caseTalk to us

Short answer

A payment provider gives you a checkout, authorisation, 3-D Secure and settlement. The first decision is how much of the checkout you build: hosted pages launch fastest with the least PCI scope, a fully custom form gives full control and more compliance work.

What this use case is

A payment provider gives you a checkout, authorisation, 3-D Secure and settlement. The first decision is how much of the checkout you build: hosted pages launch fastest with the least PCI scope, a fully custom form gives full control and more compliance work.

Who builds this

E-commerce brands
SaaS subscriptions
Digital services
Marketplaces

What your customer sees

  1. 1Enters card or taps a wallet
  2. 2Completes a 3-D Secure check if asked
  3. 3Sees confirmation
  4. 4Card is saved for next time if they agree

How Payment Processing & Acquiring solves it

1

Checkout collects card details or a wallet token

Checkout collects card details or a wallet token

2

Provider tokenises the card

Provider tokenises the card

3

Authorisation request goes to the acquirer and scheme

Authorisation request goes to the acquirer and scheme

4

3-D Secure runs where required or an exemption is applied

3-D Secure runs where required or an exemption is applied

5

Issuer approves or declines

Issuer approves or declines

6

Capture, settlement and payout to your account

Capture, settlement and payout to your account

7

Refunds and disputes handled through the same provider

Refunds and disputes handled through the same provider

Want to have

  1. Hosted or embedded checkout
  2. Card and wallet acceptance
  3. 3-D Secure with exemption handling
  4. Tokenisation and stored credentials
  5. Recurring payments if you bill repeatedly
  6. Refunds
  7. Settlement reporting
  8. Webhooks

Optional

  1. Network tokens
  2. Account updater
  3. Local payment methods
  4. Payment links

Design decisions

Checkout build

Hosted
Embedded
Custom

launch speed and PCI scope versus control.

Subscriptions

Provider's billing
Your own billing with stored credentials

less to build versus flexibility.

What to put in your RFP

Checkout

  • integration type
  • supported wallets

Authentication

  • 3-D Secure version
  • exemptions

Recurring

  • stored credentials
  • account updater

Operations

  • refunds
  • disputes
  • reporting

Commercials

  • pricing model
  • fixed fees
  • chargeback fees
Add these to an RFP

How to evaluate providers for this use case

  1. 1Integration effort for your stack
  2. 2Approval-rate tooling
  3. 3Wallet coverage
  4. 4Reporting quality
  5. 5Pricing at your basket size

Pitfalls

  • Building a custom card form and inheriting heavy PCI obligations
  • Ignoring exemptions and challenging every customer
  • Not planning for card expiry on subscriptions
  • Blended pricing that hides costs on small baskets

What providers will ask you

  1. Markets and currencies
  2. Monthly volume and average basket
  3. Recurring or one-off
  4. Current provider and history of disputes

Other Finlane categories that cover parts of this

This use case is solved mainly with Payment Processing & Acquiring. These categories cover specific parts of it and can be tendered alongside it.

Fraud & AML Monitoring

Fraud scoring on online payments

Chargebacks & Disputes

Disputes on online orders

Open Banking & Account Data

Pay-by-bank alongside cards

Frequently asked questions

Other Payment Processing & Acquiring use cases

Enable in-store or unattended payments

Combine online acquiring with SoftPOS, terminals or QR code payments across markets.

Run marketplace split payments

Split a single buyer payment across multiple sellers with automated payouts and reconciliation.

Reduce checkout friction internationally

Route transactions to local acquirers to lift authorization rates and unlock local payment methods.

Scope accept online card payments with Payment Processing & Acquiring providers

Scope this use case