Amazon SP-API Adds Payment Tracking Fields for Brazil Marketplace Orders
The Amazon SP‑API now returns three new payment fields—AcquirerId (e.g., "12.345.678/0001‑90"), AuthorizationCode (e.g., "AB123456789"), and CardBrand (Visa, Mastercard, Elo, etc.)—but only for orders on the Brazil (BR) marketplace. Credit‑card orders include all three fields; Pix orders return AcquirerId and AuthorizationCode only.
Overview
Amazon has introduced three payment‑related attributes to the Selling Partner API’s getOrders call, but only for orders placed on the Brazil (BR) marketplace. The new data points give sellers and their software partners visibility into the processor, authorization code, and card network behind each transaction, which can simplify reconciliation and reporting in Brazil’s rapidly expanding e‑commerce environment.
Key Points
- Acquirer ID added — Returns the CNPJ (Brazilian corporate tax number) of the bank or payment processor that settled the sale, e.g.,
12.345.678/0001‑90. - Authorization Code added — Supplies the unique code confirming that the issuing institution approved the payment, such as
AB123456789. - Card Brand added — Identifies the payment network used (Visa, Mastercard, Elo, etc.) for credit‑card orders; the field is omitted for Pix payments.
- Brazil‑only scope — All three fields appear exclusively in responses for BR marketplace orders; they are never returned for North America, Europe, or other regions.
- Partial availability by method — Credit‑card transactions include all three fields, while Pix transactions provide only Acquirer ID and Authorization Code.
How the New Fields Work
-
API call returns expanded PaymentExecutionDetail — When a developer invokes
getOrderswith a filter that includes Brazilian orders, the response’sPaymentExecutionDetailarray now contains three extra keys.- Example: A request for order
123‑4567890‑1234567returns"AcquirerId":"12.345.678/0001‑90","AuthorizationCode":"AB123456789", and"CardBrand":"Visa"for a credit‑card purchase.
- Example: A request for order
-
Acquirer ID provides bank identification — The value mirrors the CNPJ of the acquiring institution, enabling downstream systems to match the transaction to the exact bank used for settlement.
Analysis & Recommendations
Why This Matters
Brazilian sellers can automatically capture processor CNPJ, authorization codes and card networks, reducing manual statement reconciliation and supporting audit compliance. The new fields also allow analytics on credit‑card vs Pix usage, improving payment‑method strategy.
Key Takeaways
- AcquirerId now provides the bank's CNPJ (e.g., "12.345.678/0001‑90") in getOrders responses for BR marketplace orders.
- AuthorizationCode is returned for both credit‑card and Pix payments, giving a unique capture reference per transaction.
- CardBrand appears only for credit‑card orders (Visa, Mastercard, Elo, etc.) and is omitted for Pix transactions.
- The three fields are exclusive to marketplace ID "A2Q3Y263D00KWC" (Brazil) and never appear for other regions.
Recommended Actions
- →Update your order table schema (e.g., MySQL) to add columns acquirer_cnpj, auth_code, and card_brand as VARCHAR fields.
- →In your integration code, add a check for order.getMarketplaceId().equals("A2Q3Y263D00KWC") before mapping AcquirerId, AuthorizationCode, and CardB...
- →Modify nightly reconciliation scripts (e.g., Python) to pull auth_code from the API and compare it with bank settlement files for Brazil orders.
Comments
Join the discussion
Log in or create an account to share your thoughts on this update.
No comments yet. Be the first to share your thoughts!