--- title: "SEPA Transfers and Payments" slug: "planned-sepa-transfers-and-payments" updated: 2026-07-08T14:36:48Z published: 2026-07-08T14:36:48Z canonical: "www.documentation.paynetics.digital/planned-sepa-transfers-and-payments" --- > ## 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. # SEPA Transfers and Payments SEPA (Single Euro Payments Area) is the European payment integration framework that enables EUR transfers across 36 participating countries, including all EU member states plus Iceland, Liechtenstein, Norway, Switzerland, the UK, and several others. Paynetics supports both **inbound** and **outbound** SEPA transfers across two rails: SEPA Credit Transfer (standard) and SEPA Instant Credit Transfer. --- ## Transfer Rails ### SEPA Credit Transfer (SCT) The standard SEPA rail for EUR payments. - Processed in batches during business days - Last outbound cut-off: **15:30 CET** - Payments submitted after the cut-off or on SEPA bank holidays are processed on the next business day - Funds typically arrive within the same or next business day ### SEPA Instant Credit Transfer (SCT Inst) The real-time rail for EUR payments. - Executed within **10 seconds**, available **24/7/365** - Supported where both the sending and receiving institutions participate in SEPA Instant - If the receiving institution does not support SEPA Instant, the transfer automatically falls back to standard SEPA Credit Transfer - Maximum transaction amount: **€100,000** (per SEPA scheme rules; individual Partner limits may apply) --- ## Inbound SEPA Transfers Every Paynetics Account holder receives a unique **IBAN** assigned at Balance level. Partners and their customers can receive EUR transfers from any SEPA-participating bank using this IBAN. Inbound transfers are credited as follows: | Rail | Credit timing | | --- | --- | | SEPA Instant | Within seconds of receipt | | SEPA Credit Transfer | Same business day if received before end-of-day cut-off | --- ## Outbound SEPA Transfers To initiate an outbound SEPA transfer, submit a request to the Transfers API with the following fields: - Recipient IBAN - Recipient name - Amount and currency (EUR) - Optional reference / remittance information For GBP outbound transfers, see [Faster Payments (UK)](/docs/faster-payments-uk). --- ## Supported Countries SEPA transfers are available to and from all 36 SEPA member countries. A complete list is maintained by the European Payments Council at [europeanpaymentscouncil.eu](https://www.europeanpaymentscouncil.eu). --- ## Integration For API endpoints and step-by-step integration guides, see: - [Send a Wire Transfer](/docs/send-a-wire-transfer) — outbound SEPA - [Receive a Wire Transfer](/docs/receive-a-wire-transfer) — inbound SEPA For transfer processing times across all supported rails, see [Payment Systems and Processing Times](/docs/to-publish-payment-systems-and-processing-times). A **Partner** is the entity that integrates Paynetics’ services and offers them to end customers. Partners operate within their own instance and manage users, merchants, applications, and programs. They define fees, user flows, and configurations within the limits of their contractual agreement and may be responsible for KYC or KYB processing. The partner is the primary integrator and owner of the end-to-end solution built on Paynetics. 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. A **Balance** represents an amount of funds held in a specific currency within an account. An account may have multiple balances, typically one per supported currency. Balances are assigned payment identifiers such as IBANs or account numbers, depending on the currency. All monetary operations reference a **balance token**, which is used in API calls to debit or credit funds, perform transfers, or apply fees.