Added to Amalert: Jan 30, 2026
Amazon SP-API Adds New Payment Data Fields for Brazil Marketplace Tax Compliance
Amazon's SP-API will add a payments array to the Shipment Invoicing API and three new fields—paymentCnpj, creditCardBrand, and authorizationId—to the Orders API on January 28 2025. These Brazil‑specific attributes enable SEFAZ‑compliant invoicing by providing acquirer CNPJ, card brand, and NSU for credit‑card and Pix payments.
Overview
Amazon is rolling out new fields to two Selling Partner APIs that supply payment information for Brazil‑based sales. Effective January 28 2025, the Shipment Invoicing API and the Orders API will return detailed payment attributes required by Brazil’s SEFAZ tax authority. Sellers who generate electronic invoices for Brazilian customers must adapt their systems now to avoid compliance gaps.
Key Points
- Launch date — The updated APIs become live on January 28 2025, giving sellers a three‑month window to modify integrations.
- Payment method granularity — Each transaction will now carry a specific method code (credit card, debit card, Pix, boleto, etc.), enabling precise tax classification.
- Acquirer CNPJ inclusion — Credit‑card and Pix payments will embed the CNPJ (Brazilian corporate tax ID) of the acquiring bank, a mandatory element for SEFAZ‑approved invoices.
- Card brand identification — The brand (Visa, Mastercard, Elo, etc.) used for a card payment will be reported, supporting detailed reconciliation and reporting.
- Authorization identifier (NSU) — A unique numeric string from the acquirer will accompany credit‑card and Pix transactions, creating an auditable link between Amazon orders and payment processor records.
- Transaction amount array — A new “payments” collection will break down each payment component, listing currency code and exact value, which is essential for orders with split or partial payments.
How the API Changes Work
-
Shipment Invoicing API – payments array added — When a seller queries
getShipmentDetailsfor an FBA shipment, the response now contains apaymentsarray.- Example: For a shipment that includes a Pix payment of R$ 150.00, the array entry will show
paymentType: "Pix",paymentCnpj: "12.345.678/0001-90",amount: {currencyCode: "BRL", value: "150.00"}, andauthorizationId: "1234567890".
- Example: For a shipment that includes a Pix payment of R$ 150.00, the array entry will show
Analysis & Recommendations
Why This Matters
Brazilian sellers must capture the new CNPJ, card brand, and authorization ID to generate SEFAZ‑approved NF‑e/NF‑Ce documents, otherwise they risk fines or order suspension. The three‑month window before the Jan 28 2025 launch requires immediate integration updates and testing.
Key Takeaways
- Launch date is January 28 2025, giving sellers a three‑month migration period.
- Shipment Invoicing API now returns a payments array with fields like paymentType, paymentCnpj, amount, and authorizationId.
- Orders API paymentDetail array gains paymentCnpj, creditCardBrand, and authorizationId for CreditCard and Pix payments.
- CNPJ values must follow the pattern XX.XXX.XXX/XXXX-XX and currency codes must be ISO‑4217 (e.g., BRL).
Recommended Actions
- →Update your API parsing code (Seller Central > Developer Console > SP‑API) to map paymentCnpj, creditCardBrand, and authorizationId for Brazil orders.
- →Add CNPJ format validation using regex \d{2}\.\d{3}\.\d{3}\/\d{4}\-\d{2} in your invoicing pipeline before generating NF‑e XML.
- →Run sandbox transactions for CreditCard, Pix, and Boleto and verify the generated NF‑e includes <PaymentCNPJ> and <AuthorizationID> elements.
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!