Your first API call demonstrates how to submit a transaction check request and retrieve an immediate response on whether the transaction can proceed.
Get your API key
All API requests require authentication with an API key. See Authentication for details.
Example request
Below is an example of a JSON payload for submitting your first request:
{
"tenantProcessingTimestamp": "2022-02-17T16:13:29.000Z",
"tenantTransactionId": "Transaction will be blocked because of the country.",
"accountHoldingParty": "FUNDS_ORIGINATOR",
"fundsOriginator": {
"accountNumber": "DE70203343824781776145",
"holder": "Herbert Dzeko",
"bankCountry": "DE"
},
"fundsBeneficiary": {
"accountNumber": "BA565601471038781051",
"holder": "Martin Dzeko",
"bankCountry": "BA"
},
"settledAmount": 199,
"settledCurrency": "EUR",
"usage": "Thank you"
}
Request field descriptions
Field | Description |
---|---|
| Timestamp when the transaction was processed on the Tenant’s system. |
| Transaction ID assigned by the tenant. Can be any string or number. |
| The party that holds an account with the tenant – i.e., the Customer of your organization. Possible values: |
| Account object from which the funds are transferred (DEBIT). |
| IBAN or account number (SWIFT or domestic format). |
| Account holder’s full name. |
| ISO 3166-1 alpha-2 country code of the originator’s bank. |
| An account that receives the funds (CREDIT). |
| IBAN or account number (SWIFT or domestic format). |
| Account holder’s full name or company name. |
| ISO 3166-1 alpha-2 country code of the beneficiary’s bank. |
| Amount displayed on the customer’s bank statement (including fees/expenses). See also |
| Currency code in ISO 4217 3-letter format (e.g., |
| Free text accompanying the transaction (e.g., payment purpose or reference). |
Example response
{
"tenantTransactionId":"Transaction will be blocked because of the country",
"caseId":"fd6f0f6f-db51-4159-bd6f-d833ffb2e4cf",
"proceed":true
}
Response field descriptions
Field | Description |
---|---|
| Transaction ID provided in the reque |
| Unique UUID assigned to each transaction, regardless of whether it is suspicious or not. |
| Indicates if the transaction should be processed.
|
Further reading
Use Cases Overview – Learn how different request types fit your organization’s needs.