Skip to main content
Every operation on your account — payouts, payins, transfers, crypto deposits and withdrawals, swaps and card purchases — has a downloadable branded PDF receipt: logo, colors, the operation status and a signed verification code with a QR that anyone can check publicly to confirm the document is authentic. There is nothing to build: every response and webhook of an operation includes its receipt_url ready to download, and when the operation reaches a final state the receipt is also emailed automatically to the account owner (with opt-out).

​
Downloading a receipt

Every transactional resource with GET /{id} has its GET .../receipt. The PDF defaults to Spanish; add ?lang=en for English.
The crypto deposit depositID comes from GET /v1/crypto/transactions (each deposit’s deposit_id field, next to its receipt_url).
Only the operation’s owner (or the organization admin) can download the receipt: a foreign ID returns 404 not_found. The PDF shows the beneficiary data exactly as you submitted it.

​
receipt_url in responses and webhooks

Never build the URLs by hand: every payout, payin, transfer, withdrawal, deposit, swap and card transaction response includes receipt_url, and the final-state webhooks (payout_status_changed, payin_credited, transfer_received, crypto_deposit_credited, crypto_withdrawal_status_changed, card_transaction) carry it in the payload too.

​
Statuses and watermark

The receipt reflects the operation status at download time:
A watermarked receipt is not proof of payment: the operation has not completed yet (or it failed). Download it again after the final-state webhook and it will come out clean.

​
Authenticity verification (QR)

Every PDF carries a printed signed verification code and its QR. The QR opens a public URL — no credentials — that answers with the operation’s real, current data:
If the same URL is opened in a browser (for example by scanning the QR with a phone), it renders a branded web page with the result.
  • The response never includes the beneficiary’s personal data, accounts or addresses: only type, status, amount and date.
  • The code is cryptographically signed: a tampered or made-up one answers 404 with "valid": false.
  • The verification shows the current data: if someone edits the PDF to inflate the amount, the QR exposes it instantly.

​
Automatic receipt email

When an operation reaches a final state (completed or failed), the account owner receives an email with the PDF attached and the verification link. It applies to payouts, payins, sent transfers, crypto deposits and withdrawals and swaps (card purchases do not email, to avoid flooding your inbox). To disable it (or turn it back on) per account:

​
Errors

​
FAQ

As many times as you want: it is rendered on the fly with the operation’s current data. That is why a receipt downloaded while pending comes out watermarked, and the same endpoint returns the clean version after the final webhook.
Yes — that is what it is for. Whoever receives it can scan the QR and confirm against the platform that the document is authentic and that the status and amount are real, no credentials needed.
The PDF is only a representation: the truth lives in the platform. The QR and code carry a cryptographic signature bound to the real operation; checking them shows the true amount and status, so any tampering is exposed.
Spanish (?lang=es, default) and English (?lang=en). The email uses Spanish.
The branding of the platform you operate on (the operator’s logo, colors and contact details). The PDF/Excel statement uses the same identity.
No. The code verifies for as long as the operation exists, and it always answers its current status.
Last modified on July 13, 2026