Payment methods

Connect global and local payment methods through one integration.

Cards, wallets, bank transfers, open banking, local APMs, and payouts — accessible through a single API, with new methods added as you expand into new markets.

How methods work in Paytone

One API, every method, on your timeline.

You don't need to plumb each method individually. Methods sit behind the same payment object — turn them on when a market opens up, without rewriting the integration.

Step 01

Choose the method

Pick the methods relevant to the markets you serve. Each one has the same payment lifecycle and the same webhook shape.

Step 02

Configure a provider

Connect an acquirer or scheme partner for the method. Paytone supports multiple providers per method for routing and fallback.

Step 03

Integrate once

Use the same payments.create call with a different method string. New methods plug in without touching your checkout code.

Step 04

Expand as you grow

Add methods as you enter new markets. Routing rules, reconciliation, and reporting automatically include the new flows.

Methods, orchestrated

Methods aren't bolted on — they're orchestrated.

Every method is a first-class citizen in Paytone's routing engine. You can apply the same fallback logic, the same retry policies, and the same risk rules across cards, wallets, bank rails, and open banking — without writing separate code paths for each.

  • Unified payment object — cards, wallets, and bank rails share the same lifecycle and webhook contract.
  • Per-method routing — set rules per method, region, currency, or risk profile.
  • One reconciliation surface — finance teams reconcile every method through one report set.
How orchestration works
Get started

Add a method. Or every method.

Talk to the team about the methods you need in the markets you serve, and what it would take to ship them in your stack.