Originate a SEPA Instant Credit Transfer (SCT Inst) via a payment API and handle reject and timeout scenarios

Steps

1. 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
2. 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
3. Submit the payment and record the provider's transaction reference; SCT Inst requires the funds to reach the beneficiary within 10 seconds of acceptance
4. 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
5. 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
6. 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