Token.io

token.io ↗

Connect bank checkout to customer authorization and verified payment status

SI Score
80/100
Pricing
Contact for Pricing AI reading, not confirmed
Free plan
Not confirmed
Sign-up required
Required AI reading, not confirmed

Ask SI about Token.io

Answers use saved listing facts and recorded sources.
Homepage screenshot
Screenshot of the Token.io homepage

What it does

Token.io provides account-to-account payment infrastructure for payment providers, platforms and financial applications. Its programming interface supports single payments, recurring authorizations, account data and settlement-account operations. A dashboard account and an approved implementation are required; production access follows commercial and licensing review.

Begin with the implementation manager and develop against the sandbox. Token.io reviews the integration before providing production access. The licensing arrangement matters: a client can use Token.io's permissions and bank connections or register its own authorization and certificates; partner permissions govern onboarding other merchants.

For hosted checkout, send the payment reference, amount, currency, beneficiary details and return address. Token.io returns the payment identifier and the next authorization step. Open its hosted screens in a popup-style modal or a separate page, let the customer choose and approve the bank payment, then process the return to your site.

Follow the payment's status notification after the customer returns. With a settlement account, Settlement Completed confirms reconciliation; without one, Initiation Completed does not guarantee that funds have settled. Keep a non-final result open for later updates rather than releasing an order just because the browser journey ended.

Supported payment routes include UK Faster Payments, euro transfers through the Single Euro Payments Area, and named domestic routes such as Poland's Elixir. The selected banks, currency and account identifiers determine the route. Agree the contract charges, required business checks and settlement-account terms for the proposed countries before launch.

Strengths

  • The dashboard shows payment activity and errors filtered by date.
  • Payment initiation can specify a future execution date.
  • Variable recurring payments use an approved mandate for a series of bank charges.

Watch out for

  • Child merchants operating under a parent payment provider have no separate dashboard login and inherit its licensing configuration.
  • Instant euro transfers require both participating banks to support the instant scheme.

Best for

  • Payment providers adding bank checkout to merchant services
  • Development teams implementing consent and settlement-aware order handling

Sources