--- title: "Transfer Statuses" slug: "to-publish-transfer-statuses" updated: 2026-07-08T16:05:01Z published: 2026-07-08T16:05:01Z canonical: "www.documentation.paynetics.digital/to-publish-transfer-statuses" --- > ## Documentation Index > Fetch the complete documentation index at: https://www.documentation.paynetics.digital/llms.txt > Use this file to discover all available pages before exploring further. # Transfer Statuses Every transfer initiated through or received by Paynetics moves through a defined set of statuses. Understanding these statuses lets you build reliable payment flows, handle edge cases, and provide accurate feedback to end users. --- ## Status Reference ### Pending The transfer has been received and accepted by Paynetics but has not yet been processed or settled. Common reasons a transfer remains Pending: - The outbound transfer is queued for the next processing window (e.g., standard SEPA before cut-off) - An inbound transfer has been received but is held in the Suspense Queue for compliance review Transfers can remain Pending for a short time (seconds for Faster Payments) or until the next business day (standard SEPA submitted after cut-off). --- ### Sent The outbound transfer has been successfully submitted to the payment scheme and is on its way to the recipient. For Faster Payments and SEPA Instant, this typically means funds have already been credited to the recipient. For standard SEPA, Settlement occurs on the value date. --- ### Returned The transfer was initially sent but subsequently returned by the receiving bank. Returns occur when: - The recipient Account is closed or does not exist - The recipient bank rejected the payment (e.g., account blocked, currency mismatch) - The recipient account holder requested a return (applicable to SEPA Credit Transfers within scheme rules) When a transfer is returned, the funds are credited back to the originating account. A return reason code from the receiving bank is included where available. --- ### Rejected The transfer was rejected before it was submitted to the payment scheme. Rejection happens at the Paynetics processing layer, typically because: - Insufficient funds in the source account - The transfer failed a compliance or fraud check - A required field was missing or invalid (e.g., invalid IBAN format) - The transfer exceeded a limit configured on the Programme or account Rejected transfers are not submitted to the payment scheme and no funds leave the account. --- ### Cancelled The transfer was cancelled before processing completed. Cancellation may be initiated by: - The partner via the API (where cancellation is still possible) - Paynetics (e.g., during a compliance review) Once a transfer has reached **Sent** status, it cannot be cancelled — a return must be requested from the receiving bank instead. --- ## Status Flow ```plaintext [Initiated] → Pending → Sent ✓                      ↘ Returned (after send)             ↘ Rejected (before send)             ↘ Cancelled (before send) ``` --- ## Related Articles - [Work with Suspense Queue](/docs/suspense-queue-integration-guide) — handling inbound transfers held for review - [Send a Wire Transfer](/docs/send-a-wire-transfer) — outbound transfer API guide - [Receive a Wire Transfer](/docs/receive-a-wire-transfer) — inbound transfer handling Single Euro Payments Area. A European payment integration initiative that enables euro-denominated credit transfers and direct debits across 36 member countries under unified standards and processing rules. The actual transfer of funds between financial institutions to complete a card transaction or a batch of transactions. In the BIN Sponsorship context, settlement refers to the daily funding movement from the Programme Manager to Paynetics to cover net scheme obligations. An **Account** is a payment or e-money account used to hold funds and execute transactions. Accounts are created under a specific instance and program and are associated with either a user or a merchant. They provide the logical structure under which balances, cards, and transactions are organised. Common account purposes include: - executing card payments and transfers - holding settlement funds - pre-funding services such as OCT An account acts as a container for balances rather than holding funds directly. International Bank Account Number. A standardised international format for identifying a bank account. In the Paynetics platform, IBANs are assigned at the Balance level, allowing accounts with multiple balances to have separate IBANs per currency. The configuration object that governs the behaviour and capabilities of Accounts and the Cards linked to them. Every Account is created under a specific Programme. Programmes are configured by Paynetics during onboarding and cannot be created or modified via the API by Partners.