Skip to content

↑↓ navigate ↵ open Ctrl↵ new tab esc close

Fixed values used in every example of the documentation. Use them as a reference when reading curl samples and payloads: the same IDs appear on different pages on purpose, so that a transaction example connects to an alert example.

They all follow the same pattern, 00000000-0000-0000-0000- plus a suffix, to make it obvious they are examples. A real ID never has this format.

What it identifiesFieldValue
Transactionid, transaction_id00000000-0000-0000-0000-000000000042
Merchantmerchant_id00000000-0000-0000-0000-000000000001
Alertalert_id00000000-0000-0000-0000-000000000099
Disputedispute_id00000000-0000-0000-0000-0000000000d1
Evidenceid00000000-0000-0000-0000-0000000000e1
Your companycompany_id00000000-0000-0000-0000-0000000000c1
Merchant enrollmentmerchant_enrollment_id00000000-0000-0000-0000-0000000000aa

Transaction …042 is the same on every page: it is the one you create in Create transaction, then get, update and delete on the following pages, and it is the one the evidence points to.

FieldValue
external_id (your transaction ID)TXN-2026-001
amount150.00
currencyUSD
transaction_date2026-04-01T15:30:00Z
card_last44242
card_bin424242
descriptorLOJA EXEMPLO
arn74537119547024600128228
Customer webhook URLhttps://seu-sistema.com/webhooks/rapid
API base URLhttps://api.rapidchargeback.com/api/v1

Every example uses the same encoded header:

Authorization: Basic Y2xpZW50X2lkOmNsaWVudF9zZWNyZXQ=

The base64 value decodes to client_id:client_secret. In your code, replace it with your company’s real credentials.

  • Customer: João Silva, email joao@exemplo.com
  • Address: Rua das Flores, 123, São Paulo, SP, 01001000, BRA

These values have no special meaning; they are just placeholders that stay consistent across pages. They are in Portuguese because they are the same in every language of this documentation.