creditorId) or inline as a full creditor object. Domestic wires require an ABA routing number on the receiving bank. Every request must include a unique x-idempotency-key header to ensure safe retries without duplicate payments.
Endpoint
com.diameterpay.api/payments.write
Headers
string
required
Bearer {access_token}string
required
A unique UUID v4 for this request. Re-submitting the same key returns the original response without creating a duplicate payment. Generate a new UUID for each logically distinct payment.
Request Body
string
required
Your unique reference for this payment. Maximum 36 characters. This value travels with the wire and appears in downstream bank statements.
string
required
UUID of the Diameter virtual account that funds will be debited from.
string
required
The payment amount as a decimal string, e.g.
"100.00". Must be a positive value with up to two decimal places.string
required
The payment currency. Currently must be
USD.string
required
The Originator-to-Beneficiary Information (OBI) field. Maximum 255 characters. This text is forwarded to the receiving bank and appears on the beneficiary’s statement.
string
UUID of a previously saved counterparty. Provide either
creditorId or creditor — not both.object
Inline counterparty details. Provide either
creditor or creditorId — not both.string
Optional free-text field for supplementary payment notes. Maximum 255 characters.
Response Fields (201 Created)
string
The Diameter-issued UUID for the created payment. Use this to track status via Get Payment.
string
UUID of the counterparty record. If you provided an inline
creditor object, Diameter creates or matches a counterparty and returns its UUID here for future reuse.