Supporting documents

Every payout contains at least one supporting document. Documents are embedded in transaction.supportingDocuments[] so the evidence remains correlated with the exact payout request.

Field	Type or format	Requiredness	Description
`documentType`	String	Required	Type of evidence. Supply an accepted Axiym value or descriptive text.
`documentDescription`	String	Optional	Human-readable description or document reference.
`documentContentType`	MIME type	Required	Media type such as `application/pdf` or `image/jpeg`.
`documentData`	Base64 string	Required	Base64-encoded file content.
`documentDataBackside`	Base64 string	Optional	Back side of a two-sided document.

Example

{
  "documentType": "supplier invoice",
  "documentDescription": "Invoice INV-2026-001",
  "documentContentType": "application/pdf",
  "documentData": "JVBERi0xLjQKJcTl8uXrCg=="
}

Encode the raw file bytes once. Do not include a data-URL prefix such as data:application/pdf;base64, unless the API Reference explicitly permits it.

Axiym normalizes documentType to a final controlled value such as INVOICE before validating the payout. Exact accepted values pass through unchanged. The prepared payout returns the final document type together with a digest of the document content; it does not echo the base64 data.

Destination-specific rules can require particular document types or additional evidence. Retrieve corridor details before creating the payout and include all documents in the initial request.

Use Test payout data to check representative document types and destination requirements without creating a payout.

Example

On this page