Initiate a cross-border payment via Tink's cross-border Payments API between two European markets

domain: docs.tink.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Verify the source institution and destination country combination is supported by calling GET /api/v1/providers and filtering by capability PAYMENT_INITIATION and checking for cross-border support in the provider's capabilities array
  2. Authenticate the user and obtain an access_token with the payment:write scope for the source institution using the Tink Link authorization flow
  3. POST /api/v1/payment-requests with sourceAccount (IBAN of debtor), destinationAccount (IBAN of beneficiary), amount (in minor units), currency (ISO 4217), remittanceInformation, and creditor name
  4. Redirect the user to the payment authorization URL returned by Tink Link; the user authenticates via their bank's SCA flow (redirect or decoupled depending on the institution)
  5. After authorization, poll GET /api/v1/payment-requests/{paymentRequestId}/payments until the payment reaches a terminal status (PENDING, INITIATED, or FAILED); INITIATED means the payment instruction was accepted by the bank but settlement is asynchronous
  6. Handle EUR payments via SEPA Credit Transfer rules; cross-border payments within the SEPA zone must comply with the EU Instant Payments Regulation's expectation that all Eurozone PSPs support instant payments — check whether the receiving bank is instant-capable via the provider metadata

Known gotchas

Related routes

Implement SWIFT ISO 20022 pain.001 payment origination through a corporate-to-bank FileAct channel for cross-border batch payments
swift.com · 6 steps · unrated
Implement cross-border recipient management for Stripe Connect payouts in non-US geographies
stripe.com · 6 steps · unrated
Initiate multi-currency global payouts via the Airwallex Payouts API
www.airwallex.com · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans