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
Authenticate the user and obtain an access_token with the payment:write scope for the source institution using the Tink Link authorization flow
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
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)
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
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
Tink cross-border payments route via SEPA CT within Europe; non-EUR payments (e.g., GBP to EUR) involve FX conversion with rates set by the ASPSP at time of execution — the rate shown at payment initiation may differ from the executed rate
Not all provider combinations support cross-border; Tink's routing layer handles some cross-currency flows but gaps exist, particularly for non-SEPA-zone currencies — always check provider capabilities at runtime rather than hardcoding supported corridors
SEPA Instant (SCT Inst) has per-transaction amount limits set by individual ASPSPs even though the scheme allows high amounts; validate the amount against the source institution's published SCT Inst limit before initiating to avoid uninformative rejections
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp