Requirements

Fetch the receipt after the user completes the payment flow. Use the id returned in step 1 (or the flow_id from the callback URL).

GET https://api.finx-s.qwist.cloud/payment-receipts/{id}

Authorization: Basic {Base64(clientId:clientSecret)}

Response

{
  "id": "3ca31c37-986a-454e-ad64-8e97143c86bc",
  "debtor": {
    "iban": "DE93300308800013441006"
  },
  "creditor": {
    "iban": "DE93300308800013441006",
    "name": "John Doe"
  },
  "amount": {
    "value": 23.99,
    "currency": "EUR"
  },
  "purpose": "Thanks for all the fish.",
  "sepa_purpose_code": "GDDS",
  "end_to_end_reference": "5B5U3FFS9EA2LS0O",
  "submitted_at": "2026-06-04T21:18:20.358Z",
  "type": "SEPA transfer"
}

Field reference:

submitted_at reflects submission time, not settlement. For SEPA Instant transfer, settlement typically occurs within seconds. For SEPA transfer, settlement happens during the bank's next booking cycle, usually within a few hours on business days.

Important notes

🚧

1-hour availability window

The payment receipt is only available for 1 hour after the payment is successfully submitted. Fetch it promptly after receiving the success callback. If you miss the window, there is no way to retrieve it.

📘

Not a settlement confirmation

The receipt confirms the payment was submitted to the bank - not that funds have settled. For SEPA transfer, the bank may still reject it during the booking process (e.g. insufficient funds). For SEPA Instant transfer, rejections are returned faster but are still possible. Use end_to_end_reference for downstream reconciliation.

📘

404 while the flow is in progress

This endpoint returns 404 while the user is still going through the Widget. This is expected - only poll after you receive the success callback.

{
  "error": {
    "code": 1000,
    "group": "client",
    "description": "Request body doesn't match input schema.",
    "data": {
      "redirect_uri": ["Not a valid URL."]
    }
  }
}