Simulating account services
Build and test your integration to account services at Banking Circle
Agency Banking Whitelisting
Workflows related to whitelisting of self-issued IBANs or accounts for Agency Banking. Use the below scenarios to test both successful- and failed whitelisting requests, as well as scenarios related to account holder verification.
The simulator validates the following:
- User access to the given Company Number
- Required properties as per the API reference
- Maximum number of accounts per request (1000)
- Duplicate accounts/IBANs
Scenarios
| Scenario | Step | HTTP Request | Input parameters | HTTP Response | Status | Comment |
|---|---|---|---|---|---|---|
| SUCCESS | ||||||
| 1 | POST | Any valid parameters | 202 (Accepted) | N/A | ||
| 2 | GET | requestId | 200 (OK) | "Pending" | The status will be Pending until 4 seconds after the related request was submitted. | |
| 3 | GET | requestId | 200 (OK) | "Succeeded" and "Pending" | After 4 seconds, accounts in the request will gradually change to Succeeded | |
| 4 | GET | requestId | 200 (OK) | "Succeeded | After 8 seconds, all accounts will be in status Succeeded | |
| REJECTED | ||||||
| 1 | POST | "ncc": "Error" | 202 (Accepted) | N/A | Set the value of the "ncc" property to "Error" to trigger a rejection scenario, as explained below. | |
| 2 | GET | requestId | 200 (OK) | "Pending" | The status will be Pending until 4 seconds after the related request was submitted. | |
| 3 | GET | requestId | 200 (OK) | "Rejected" and "Pending" | After 4 seconds, accounts in the request will gradually change to Rejected | |
| 4 | GET | requestId | 200 (OK) | "Rejected" | After 8 seconds, all accounts will be in status Rejected |
Account Aliases (PayID, etc)
Workflows related to the creation and management of PayID aliases for Banking Circle-issued accounts. Use the below scenarios to test both successful- and failed PayID requests.
Scenarios
| Scenario | Step | HTTP Request | Input Parameters | HTTP Response | Status | Comment |
|---|---|---|---|---|---|---|
| SUCCESS | ||||||
| 1 | PUT | Any valid input parameters | 202 (Accepted) | "PENDING" | PUT operation returns a traceId to be used for subsequent GET calls | |
| 2 | GET | traceId | 200 (OK) | "COMPLETED" | ||
| ERROR | ||||||
| 1 | PUT | Name with prefix "ERROR -", e.g. "ERROR - John Doe" | 202 (Accepted) | "PENDING" | PUT operation returns a traceId to be used for subsequent GET calls | |
| 2 | GET | traceId | 200 (OK) | "FAILED" | ||
| DELAY | ||||||
| 1 | PUT | Name with prefix "DELAY -", e.g. "DELAY - John Doe" | 202 (Accepted) | "PENDING" | PUT operation returns a traceId to be used for subsequent GET calls | |
| 2 | GET | traceId | 200 (OK) | "PENDING" | The status will be PENDING until 2 minutes after the related request was submitted. | |
| 3 | GET | traceId | 200 (OK) | "COMPLETED" | After 2 minutes, the status will change to COMPLETED |
Updated 1 day ago