TransactionsBanking Transaction Receipt

Banking Transaction Receipt

Generates the PDF receipt for a banking transaction (Pix, TED, transfer between Conta Simples accounts, or bill payment) and returns a short-lived signed URL to download it.

Rules:

  • Receipts are only available for transactions with status PROCESSED (status: 2).
  • Check the transaction's showReceipt field (in the banking statement) before calling — it indicates whether the operation generated a receipt.
  • The download URL is signed and expires in 5 minutes (see expiresAt); issue a new request if it expires.
  • Transaction types without a supported receipt return 404.
curl -X GET "https://api-sandbox.contasimples.com/statements/v1/banking/106615/receipt" \
  -H "Content-Type: application/json" \
  -H "Signature-Input: example_string" \
  -H "Signature: example_string" \
  -H "Authorization: Bearer YOUR_API_TOKEN"
{
  "downloadUrl": "https://banking-transaction-receipts.s3.amazonaws.com/company-id/106615.pdf?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Expires=300&X-Amz-Signature=...",
  "expiresAt": "2026-07-16T18:52:50.000Z"
}
GET
/statements/v1/banking/{transactionId}/receipt
GET
Base URLstring

Target server for requests. Edit to use your own host.

Bearer Token
Bearer Tokenstring
Required

Bearer token from OAuth 2.0 client credentials. Format: Bearer TOKEN

Bearer token from OAuth 2.0 client credentials. Format: Bearer TOKEN
path
transactionIdinteger
Required

Banking transaction ID, obtained from the transactions array in the banking statement response.

header
Signature-Inputstring

What was signed and the signature parameters, in the RFC 9421 format. A credential with a public key must send it on every call, reads included, or the request is refused with 401. The signature covers the @method, @path, and @query components, and also content-digest when there is a body. created and alg are required, and created is valid for 300 seconds. The full format, with examples, is in Request Signing.

header
Signaturestring

The signature of the base defined by RFC 9421, in base64, between : and under the same label used in Signature-Input, for example sig=:SGVsbG8gd29ybGQ=:. It always goes together with Signature-Input.

Request Preview
Response

Response will appear here after sending the request

Authentication

header
Authorizationstring
Required

Bearer token. Bearer token from OAuth 2.0 client credentials. Format: Bearer TOKEN

Path Parameters

transactionIdinteger
Required

Banking transaction ID, obtained from the transactions array in the banking statement response.

Example:
106615

Headers

Signature-Inputstring

What was signed and the signature parameters, in the RFC 9421 format. A credential with a public key must send it on every call, reads included, or the request is refused with 401. The signature covers the @method, @path, and @query components, and also content-digest when there is a body. created and alg are required, and created is valid for 300 seconds. The full format, with examples, is in Request Signing.

Signaturestring

The signature of the base defined by RFC 9421, in base64, between : and under the same label used in Signature-Input, for example sig=:SGVsbG8gd29ybGQ=:. It always goes together with Signature-Input.

Responses

downloadUrlstring
Required

Short-lived signed URL to download the receipt PDF.

expiresAtstring
Required

Date and time (ISO 8601) when the download URL expires (default: 5 minutes after generation).