Skip to main content
POST
Confirm or reject a inbound INST payment

Overview

This endpoint processes inbound SEPA Instant payments that require confirmation. When instant payment confirmation is enabled for your account, incoming SEPA Instant payments will be held in pending_confirmation status until you respond with an acceptance or rejection.

Requirements

  • Payment must have pending_confirmation status
  • Response must be sent within 5 seconds of receiving the webhook notification
  • Valid reason code required for rejections
  • Only applicable to SEPA Instant payments with confirmation feature enabled

Response Time Critical

SEPA Instant payments have a 10-second end-to-end processing requirement. You must respond within 5 seconds to allow time for processing and sending the pacs.002 message to CSM.

How It Works

  1. Incoming Payment Received: When a SEPA Instant payment arrives and your account has confirmation enabled, the payment enters pending_confirmation status
  2. Webhook Notification: You receive a webhook with:
  • Transaction ID
  • Transaction Status (pending_confirmation)
  • Debtor Account Number
  • Creditor Account Number
  1. Your Response: Call this endpoint to accept or reject the payment
  2. Settlement: We send the pacs.002 message to CSM and update the payment status

What Happens If You Don’t Respond

How inbound SEPA Instant payments are answered is configured per tenant during onboarding. There are four modes:
  • Automatic accept: every inbound Instant payment is accepted immediately. No pending_confirmation status, no response needed from you.
  • Automatic reject: every inbound Instant payment is rejected immediately (used for example while a tenant is not yet ready to receive Instant payments).
  • Delayed automatic response: the payment is held in pending_confirmation and you answer via this endpoint within the 5-second response window. If you do not answer in time, the platform answers for you with the configured fallback: either automatic accept, or automatic reject with a configured reason code (AC01 by default).
  • Manual confirmation: the payment is held in pending_confirmation and you answer via this endpoint within the same 5-second window. If no response is received in time, the payment times out and is rejected to the clearing system.
If you are unsure which mode and fallback apply to you, ask us before going live, as it determines whether a slow response on your side results in accepted payments you did not explicitly confirm, or in rejected payments.

Path Parameters

id
integer<int64>
required

Transaction ID

Body

application/json
response
enum<string>
required

Allowed values: REJECT, ACCEPT

Available options:
ACCEPT,
REJECT
rejectReason
enum<string> | null

Rejection reason

Available options:
AC01,
AC04,
AC06,
AG01,
AG02,
AM05,
BE04,
MD07,
MS02,
MS03,
RC01,
RR01,
RR02,
RR03,
RR04

Response

Payment confirmation processed successfully

Last modified on September 2, 2026