Skip to main content
POST
/
transactions
Execute transaction
curl --request POST \
  --url https://api.example.com/transactions \
  --header 'Content-Type: application/json' \
  --data '
{
  "correlationId": "019bdb2a-960f-789d-8955-21720e6cdef0",
  "referenceId": "PAY-123456",
  "referenceSource": "PAYMENT",
  "postings": [
    {
      "source": "CUSTOMER:019bdb2a-960f-789d-8955-21720e6cdeee:019bdb2a-960f-789d-8955-21720e6cdeed:CURRENT",
      "destination": "INTERNAL:REVENUE:FEE",
      "amount": 10000,
      "currency": "EUR",
      "details": "Payment for invoice #67"
    }
  ]
}
'
{
  "type": "https://api.ledger.finventi.com/errors/bad-request",
  "title": "Bad Request",
  "status": 400,
  "detail": "Invalid request body: correlationId is required",
  "instance": "/accounts/019bdb2a-960f-789d-8955-21720e6cdeed"
}

Body

application/json

Request to execute a transaction with one or more postings

​
correlationId
string<uuid>
required

Unique identifier received from party along with initial request for transaction. Used for idempotency.

Example:

"019bdb2a-960f-789d-8955-21720e6cdef0"

​
referenceId
string
required

Reference identifier linking transaction to its origin. For payment-originated transactions, this contains the payment identification. Used to trace transactions back to their source system.

Example:

"PAY-123456"

​
referenceSource
enum<string>
required

Source system that initiated the transaction

Available options:
PAYMENT,
CLIENT,
PLAIS,
PAYMENT_CARD
​
postings
object[]
required

List of postings (debits and credits) that make up the transaction

Required array length: 1 - 100 elements

Response

Transaction execution request accepted