API Details
When working with this endpoint note that:
- Unlike the Direct Debit payment API, Beneficiary and CT requests do not require a Creditor Scheme ID or SUN reference.
- Before you can initiate a payment via the Create Credit Transfer request you must first create a beneficiary.
- Alternatively it is possible to generate a new beneficiary and a payment in a single request. See the Create Credit Transfer and Beneficiary request.
- At its most basic, a beneficiary requires a name and a bank account reference. Additional data may also be stored but is not mandatory (address details and contact details, for example).
- If you specify domestic account details for a GBP beneficiary account, specify the Sort Code in
domesticBranchCode(do not usedomesticBankCode).
Idempotency
The Idempotency check is only against successful requests, so where a previous call has resulted in any of the following HTTP Response Codes, that Idempotency key may be reused without any issue:
401403404408500501503
When working with our APIs, please use the Sandbox URI when testing and the Live URI when you move to Production.
LIVE https://api.nuapay.com SANDBOX https://sandbox.nuapay.com/
If you haven't done so already and would like to do some testing, please Request Sandbox Access
Important: Endpoints and Webhooks may be extended from time to time and any changes we make will follow our Versioning and Backward Compatibility rules. This means that the code that you write today must be designed to be robust enough to handle any future changes (where a new object is added to (or removed from) a specific API response, for example).
We now offer API Version 2 (V2) with asynchronous Credit Transfer processing for better performance. We encourage new clients to implement V2. Existing clients can continue using Version 1 (V1) with synchronous processing, which will continue to be supported. For more information or assistance, please contact support.