Credit Transfer transactions move through various statuses in their lifecycle; these are described in this section.
Overview
Nuapay supports both standard and express Credit Transfer schemes in both EUR and GBP currencies.
- Standard schemes use a file-based approach to pass payments from Nuapay to the required Scheme for processing.
- Express schemes use REST APIs.
- Standard schemes can take from one to two business days to clear; express payments are processed in seconds.
Note: All merchant/partner interactions with Nuapay are via REST. Where a payment is created against a standard file-based scheme, Nuapay will batch those payments into an appropriate file for onward processing. Your interaction in setting up the payment or retrieving its status later, for example, is all done through APIs.
The following table summarises the differences across the supported CT schemes:
Currency | Type | Scheme | Availability | Underlying Channel | Funds Credited |
EUR | Standard | SEPA Credit Transfer | Monday - Friday | File-based (ISO XML file) | Typically 1 business day* |
EUR | Express | SEPA Credit Transfer Instant | 24/7/365 | APIs | Instantly |
GBP | Standard | Bacs Direct Credit | Monday - Friday | File-based (flat file) | 2 Business Days* |
GBP | Express | Faster Payments | 24/7/365 | APIs | Instantly |
* The SEPA Credit Transfer and the Bacs Direct Credit schemes are subject to non-processing dates throughout the year. See Non-Processing Days for more details |
Tip: If a SEPA Credit Transfer is created early on a business day (before the cut-off time of 08:00 GMT) the payment will typically be credited to the beneficiary on the same day. Note that Nuapay apply Daylight Savings Time (DST) during the summer months (which is commonly referred to as British Summer Time (BST)). BST runs from the last Sunday in March to the last Sunday in October. During this period the cut off time is actually GMT -1 (so 07:00 GMT); during the period from November to the end of March, the cut off time is 08:00 GMT.
All Credit Transfer Statuses
Note that in:
- EXPRESS schemes, transactions can move from
PENDING
toPENDING_SETTLEMENT
toACCEPTED
(orREJECTED
). - STANDARD schemes, transactions can move from
PENDING
toREADY FOR EXPORT
toEXPORTED
toACCEPTED
(orREJECTED
).
Status | Description |
PENDING |
Future-dated payments are initially created in pending status.
|
READY FOR EXPORT |
Only applicable for Standard schemes:
|
EXPORTED |
Only applicable for Standard schemes:
|
PENDING_SETTLEMENT |
Only applicable for Express schemes:
|
ACCEPTED |
Where a payment has not been rejected, The CT status is updated to Accepted on its execution date. |
REJECTED |
If the payment cannot be made e.g. the beneficiary account is closed, the payment will transition to Rejected.
|
RECALLED |
A standard payment has been cancelled prior to being sent to the Scheme for further processing.
|
CANCELLED |
A standard payment has been cancelled AFTER export to the scheme, where the SEPA Reason Code is one of the following: `CUST`, `CUTA`, `DUPL`, `UPAY`.
|
Tip: SEPA and Bacs are file-based schemes and once you have created a set of CT payments for a specific execution date, your transactions are combined into either a PAIN.001 XML file (SEPA) or a Standard-18 (STD-18) flat file format (Bacs) and passed to the appropriate Clearing system for further processing. This is all managed in the background for you and you do not need to interact with these files. They are just referenced here to give some background as to when and why statuses transition, especially from
READY_FOR_EXPORT
to EXPORTED
.