Receipts and Reconciliation - OneClickDz Flexy API

Receipt

Once a transaction is SUCCESS, its receiptUrl points to GET /v3/bills/transactions/{transactionId}/receipt. The response is the file itself, not a JSON envelope.

curl https://api.oneclickdz.com/v3/bills/transactions/68cdf0a2b7c1e4d5f6a7b8c9/receipt \
  -H "X-Access-Token: YOUR_API_KEY" \
  --output receipt.pdf

Header	Value
`Content-Type`	`application/pdf`, `image/png` or `image/jpeg`
`Content-Disposition`	`attachment; filename="…"`
`Cache-Control`	`private, max-age=86400`

Read Content-Type to decide the file extension. Sandbox receipts are PNG images. Errors keep the JSON envelope: 404 NOT_FOUND when the transaction is not yours, is not SUCCESS, or has no receipt. Store the file together with operationId and transactionId. Give your customer the receipt, not just a confirmation message.

AADL payment notice

For AADL transactions, GET /v3/bills/transactions/{transactionId}/avis returns the biller’s avis de paiement as a PDF. It is available as soon as the discovery is READY, so you can show the notice before the customer pays.

curl https://api.oneclickdz.com/v3/bills/transactions/68cdf0a2b7c1e4d5f6a7b8c9/avis \
  -H "X-Access-Token: YOUR_API_KEY" \
  --output avis.pdf

404 NOT_FOUND for any other biller, for an unknown transaction, or while the notice is not available yet.

History

GET /v3/bills/transactions lists your transactions, newest first, scoped to your key’s environment.

Query	Description
`status`	One status: `PENDING`, `READY`, `PROCESSING`, `UNKNOWN`, `SUCCESS`, `FAILED`, `REFUNDED`
`partner`	One partner name
`from`, `to`	ISO 8601 bounds on `createdAt`
`limit`	1 to 100, default 20
`offset`	Default 0

curl "https://api.oneclickdz.com/v3/bills/transactions?status=SUCCESS&from=2026-09-20T00:00:00Z&to=2026-09-21T00:00:00Z&limit=100" \
  -H "X-Access-Token: YOUR_API_KEY"

meta carries total, limit and offset for pagination.

Each row carries the same fields as GET /v3/bills/transactions/{transactionId}, including bills, selectedBills and error.

Daily reconciliation

List yesterday’s transactions with status=SUCCESS, paging with offset.
Match each transactionId against your own ledger. Compare total with what you charged your customer.
List status=REFUNDED and make sure each one is refunded on your side too.
List status=UNKNOWN and keep them open until they resolve.

Any SUCCESS you do not have on your side is a payment you accepted but did not record; any record on your side without a SUCCESS is money you should not have taken.

Next: Sandbox testing

Reproduce every outcome with test accounts

​Receipt

​AADL payment notice

​History

​Daily reconciliation

Next: Sandbox testing

Receipt

AADL payment notice

History

Daily reconciliation