Create a payment
POST/api/payout_transaction_details
This endpoint is intended to create a new payment.
Prerequisites:
To use this endpoint you need to have the PAYMENT_CREATE scope for the API Key. Please contact your relation manager to get this permission.
Request Parameters:
Beneficiary Object is represented as Contact Object.
- beneficiary.type : specifies the type of beneficiary and can be either "legal_entity" or "person"
- beneficiary.country : indicates the two-letter ISO country code of the beneficiary's country (e.g., "CH" for Switzerland)
- either bankAccount.iban or bankAccount.accountNumber is mandatory
Payment signoff
- Default: payments created with API are not signed off, they must be signed off in amnis Web App before being processed
- PEER: payments created with API to an IBAN of current amnis customers are automatically signed and immediately processed as PEER payment. Learn more here about amnis PEER.
Request
Header Parameters
Possible values: <= 50 characters
An optional unique identifier for the request, limited to 50 characters. Used to track requests and prevent duplication.
- application/json
Body
required
- Array [
- ]
If left empty, the next possible execution date will be selected automatically
Possible values: >= 3 characters and <= 140 characters
This text will be seen by the beneficiary
Possible values: <= 4 characters, [DEBT, SHAR, CRED]
For LOCAL payments leave it empty, for SWIFT payments provide a value
beneficiary objectnullable
bankAccount objectnullablerequired
additionalFields object[]nullable
This should be a unique ID used to identify this payment in your system.
Responses
- 201
- 400
- 401
- 403
- 422
Created - The request was processed successfully.
- application/json
- Schema
- Example (from schema)
Schema
- PayoutTransactionDetail-PayoutTransactionDetailView
- WalletTransactionDetail-WalletTransactionDetailView
Possible values: [created, pending, transferred, canceled, pending_execution, executed, execution_error]
If left empty, the next possible execution date will be selected automatically
This text will be seen by the beneficiary
Possible values: [DEBT, SHAR, CRED]
For LOCAL payments leave it empty, for SWIFT payments provide a value
beneficiary objectnullable
Possible values: [sender, receiver]
Possible values: [created, pending, transferred, canceled]
{}
Bad Request -- Your request is invalid.
- application/json
- Schema
- Example (from schema)
Schema
{
"title": "string",
"type": "string",
"detail": "string"
}
Unauthorised -- Your access token is wrong.
- application/json
- Schema
- Example (from schema)
Schema
{
"type": "string",
"title": "string",
"detail": "string"
}
Forbidden -- Access to the requested resource or action is forbidden.
- application/json
- Schema
- Example (from schema)
Schema
A short, human-readable summary of the problem.
A human-readable explanation specific to this occurrence of the problem.
Default value: 400
A URI reference that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.
A URI reference that identifies the problem type
{
"title": "string",
"detail": "string",
"status": 400,
"instance": "string",
"type": "string"
}
Unprocessable Content -- We could not process your request due to invalid data provided.
- application/json
- Schema
- Example (from schema)
Schema
- Array [
- ]
Default value: 422
violations object[]
The property path of the violation
The message associated with the violation
The code of the violation
An extra hint to understand the violation
payload object
The serialized payload of the violation
The serialized payload of the violation
{
"status": 422,
"violations": [
{
"propertyPath": "string",
"message": "string",
"code": "string",
"hint": "string",
"payload": {}
}
],
"detail": "string",
"type": "string",
"title": "string",
"instance": "string"
}