Confirm your bank or payment provider is an SCT Inst scheme participant and that the beneficiary's IBAN is reachable on the TIPS or RT1 infrastructure using the provider's beneficiary reachability check endpoint or the EPC directory
Construct the payment request with the beneficiary IBAN, BIC if required by the provider, amount in EUR (SCT Inst is EUR only), end-to-end ID, and remittance information; SCT Inst maximum transaction amount is defined by the scheme — check current EPC rules
Submit the payment and record the provider's transaction reference; SCT Inst requires the funds to reach the beneficiary within 10 seconds of acceptance
Consume the provider's webhook or poll the transaction status endpoint: ACSC (accepted, settlement completed) is the successful terminal state; RJCT (rejected) contains an XML reason code in the ISO 20022 pacs.002 payload
For RJCT, parse the StatusReasonInformation/Reason/Code element — common codes include AM04 (insufficient funds), AC01 (invalid creditor account), and AGNT (agent not reachable on SCT Inst) — and surface a localized error message
Implement a timeout handler for non-responses: if no terminal status is received within a configurable window (e.g., 30 seconds), query the provider's status endpoint; if still pending, do not re-submit — wait for the authoritative outcome before taking any action
Known gotchas
Not all SEPA-reachable banks participate in SCT Inst; a beneficiary with a valid IBAN may still result in an AGNT rejection if their bank is not an SCT Inst participant — always check reachability before submitting rather than relying on rejection as the discovery mechanism
SCT Inst transactions cannot be cancelled after acceptance; there is no camt.056 recall mechanism for instant payments in the same way as standard SCT — fund recovery requires a manual request to the beneficiary's bank
The 10-second processing SLA is measured from the time the clearing infrastructure accepts the message, not from when your API call is made; network latency between your system and the provider adds to the effective end-user wait time
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