As Origix IP has no visibility of the accounts held by your financial institution, the system:
- Makes an API request to an Endpoint configured by your bank/financial institution to validate the provided beneficiary account.
- This configured Endpoint will need to consume the Origix IP requests and respond to them appropriately.
- If the account is valid and can receive the SCT Inst payment then the Endpoint should respond to Origix IP with a
- Where the response to the Origix IP request is a
400 - Account is invalid(or a
500 - Server could not process the request), the payment will be rejected; a REJECT notification will be dispatched from Origix IP to the CSM.
Accounts may fail validation for various reasons. For a table listing the possible return codes, expand the
400 Account is invalid link from the API Responses section below.
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 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).