The Fulfillment Outbound API now supports MCF Orders for India
Amazon refreshed the Fulfillment Outbound v2020-07-01 API to require a new paymentInformation object for Multi‑Channel Fulfillment orders to India (marketplaceId A21TJRUUN4KGV). The payload must include currencyCode "INR", amount (e.g., "3199.00") and paymentMethod "AmazonPay", otherwise the API returns an InvalidPaymentInformation error.
Overview
Amazon has refreshed the Fulfillment Outbound v2020‑07‑01 API to accept a new PaymentInformation element, making it possible for sellers to submit Multi‑Channel Fulfillment (MCF) orders that ship to buyers in India. The revised Use‑Case Guide and Dynamic Sandbox Guide now contain detailed walkthroughs for building, testing, and executing these India‑specific orders. Sellers who rely on MCF for Indian customers must modify their integration to include the payment block, or risk order failures and potential service disruption.
Key Points
- PaymentInformation field introduced — Every MCF order aimed at the India marketplace must now contain a structured payment object that records currency, amount, and payment method.
- Dedicated India tutorial added — The updated guides provide step‑by‑step instructions, sample payloads, and error‑handling tips for creating and sandbox‑testing Indian MCF orders.
- Other marketplaces unchanged — The new requirement applies only to India; existing MCF flows for the United States, Europe, Japan, and other regions continue to operate without the extra field.
- Sandbox validation enabled — Developers can now emulate India‑bound MCF orders in the sandbox, confirming that payment data is correctly formatted before moving to production.
- Regulatory compliance addressed — Incorporating payment details aligns the API with India’s tax and payment rules, lowering the chance of order rejections due to missing financial information.
- Error codes updated — The API may return a new
InvalidPaymentInformationerror when the payment block is absent or malformed, giving sellers a clear signal to correct the request.
How the Updated Fulfillment Outbound API Works
-
Activate the v2020‑07‑01 endpoint — Point your integration to the latest version of the outbound service.
- Example: Change the base URL in your HTTP client to
https://sellingpartnerapi-na.amazon.com/fba/outbound/v2020-07-01/.
- Example: Change the base URL in your HTTP client to
Analysis & Recommendations
Why This Matters
Without the paymentInformation block, India‑bound MCF orders will be rejected, causing order failures and potential revenue loss. Adding the field restores automated order flow, ensures compliance with Indian tax/payment rules, and enables sandbox validation before production rollout.
Key Takeaways
- New paymentInformation object (currencyCode, amount, paymentMethod) is required for India MCF orders.
- Marketplace identifier for India is A21TJRUUN4KGV; other marketplaces remain unchanged.
- API now returns a new InvalidPaymentInformation error when the payment block is missing or malformed.
- Sandbox now supports India‑specific MCF order testing with sample payloads and error‑handling guidance.
Recommended Actions
- →Update your order‑creation code to append a paymentInformation JSON block when marketplaceId equals A21TJRUUN4KGV (e.g., in Seller Central > API In...
- →Run the new India tutorial in the SP‑API documentation: submit a sandbox POST to https://sellingpartnerapi-na.amazon.com/fba/outbound/v2020-07-01/c...
- →Add handling for the InvalidPaymentInformation error in your error‑handling logic and log the full request payload for quick remediation.
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!