Amazon Developer

Console

as

Settings
Sign out
Notifications
Alexa
Amazon Appstore
Ring
AWS
Documentation
Support
Contact Us
My Cases

Console

as

Docs
Resources
Ecommerce Plug-ins
Publish
Connect

Combo Store Validation Plan (App Entry + Credit Card Entry)

Disclaimer: This document contains sample content for illustrative purposes only. Organizations should follow their own established best practices, security requirements, and compliance standards to ensure solutions are production-ready.

Summary

This validation plan is designed for existing partners who have pre-built integrations and do not need to build from scratch. It provides a focused subset of the full Combo Store Test Plan to validate that the partner's integration is correctly configured and functioning for a store that supports both app-based entry and credit card entry.

Use this plan when:

  • A partner has already built the integration for both entry methods
  • The store is being onboarded using an existing partner solution
  • You need to confirm connectivity, configuration, and end-to-end flow correctness for both entry paths without re-testing the full build

APIs Under Validation

API Endpoint Validation Focus
Verify Identity Keys POST /v1/identity/identity-keys Connectivity, valid/invalid key handling (app entry)
Shopper Authorization POST /v1/fraudandabuse/shopperauthorization Connectivity, APPROVED/DENIED responses (CC entry)
Create Purchases POST /v1/order/purchases Connectivity, pricing accuracy, empty cart handling
Adjust Charge POST /v1/adjust/charge Connectivity, APPROVED/DECLINED handling
Cancel Charge POST /v1/cancel/charge Connectivity, empty cart cancellation
Capture Charge POST /v1/capture/charge Connectivity, successful capture
Refund POST /v1/refund Connectivity, successful refund
Report Payment Status POST /v1/feedback/payment-status Connectivity, accepted response
Get Transactional Data POST /v1/payment/transactional-data Connectivity, data retrieval
Get Shopper Identity POST /v1/identity/shopper Connectivity, email retrieval

1. Connectivity Validation

1.1 Verify Identity Keys API Reachable

Test Case ID: VAL-CONN-001 Objective: Verify the partner can invoke the Verify Identity Keys API (app entry)

Test Steps:

  1. Call POST /v1/identity/identity-keys with a valid test identity key
  2. Verify HTTP 200 response

Expected Result: API responds without authentication or network errors

1.2 Shopper Authorization Connector Reachable

Test Case ID: VAL-CONN-002 Objective: Verify Amazon can invoke the partner's Shopper Authorization Connector (CC entry)

Test Steps:

  1. Trigger the Merchant Portal connectivity test for the F&A Connector
  2. Verify successful response

Expected Result: Connectivity test passes; HTTP 200 returned

1.3 Ordering Connector Reachable

Test Case ID: VAL-CONN-003 Objective: Verify Amazon can invoke the partner's Ordering Connector

Test Steps:

  1. Trigger the Merchant Portal connectivity test for the Ordering Connector
  2. Verify successful response

Expected Result: Connectivity test passes; HTTP 200 returned

1.4 Payment Service APIs Reachable

Test Case ID: VAL-CONN-004 Objective: Verify the partner can invoke Amazon's Payment Service APIs

Test Steps:

  1. Call POST /v1/adjust/charge with a valid test shoppingTripId
  2. Verify HTTP 200 response (or expected 400 for test data)

Expected Result: API responds without authentication or network errors

1.5 Get Transactional Data and Get Shopper Identity APIs Reachable

Test Case ID: VAL-CONN-005 Objective: Verify the partner can invoke data retrieval APIs

Test Steps:

  1. Call POST /v1/payment/transactional-data with a valid test shoppingTripId
  2. Call POST /v1/identity/shopper with a valid test shopperId
  3. Verify HTTP 200 responses

Expected Result: Both APIs respond with expected data

2. App Entry Validation

2.1 Valid Identity Key — Successful Entry

Test Case ID: VAL-APP-001 Objective: Verify a valid identity key is accepted and shopper is authorized

Test Steps:

  1. Call Verify Identity Keys with a valid base64-encoded identity key
  2. Verify response contains VALID status
  3. Verify gate opens

Expected Result: HTTP 200; identity verified; gate opens

2.2 Invalid Identity Key — Entry Denied

Test Case ID: VAL-APP-002 Objective: Verify an invalid identity key is rejected

Test Steps:

  1. Call Verify Identity Keys with an invalid or expired identity key
  2. Verify response indicates invalid key

Expected Result: Entry denied; appropriate error response

3. Credit Card Entry Validation

3.1 Approve Low-Risk Shopper

Test Case ID: VAL-CC-001 Objective: Verify the partner's F&A Connector returns APPROVED for a low-risk shopper

Test Steps:

  1. Simulate a gate entry with a low-risk shopper (no outstanding balance)
  2. Verify the connector returns shopperAuthorized: true

Expected Result: Gate opens; pre-auth placed

3.2 Deny High-Risk Shopper (Bad Debt)

Test Case ID: VAL-CC-002 Objective: Verify the partner's F&A Connector returns DENIED for a shopper with outstanding debt

Test Steps:

  1. Simulate a gate entry with a shopper who has outstanding balance
  2. Verify the connector returns shopperAuthorized: false

Expected Result: Gate remains closed

4. Charge Calculation Validation (Create Purchases)

4.1 Single Item Cart — Correct Pricing

Test Case ID: VAL-OP-001 Objective: Verify correct pricing for a single item

Test Steps:

  1. Send a Create Purchases request with one known-price item
  2. Verify purchaseId is returned and price is correct

Expected Result: HTTP 201; purchaseId returned; price correct

4.2 Multi-Item Cart with Promotions

Test Case ID: VAL-OP-002 Objective: Verify promotions are applied correctly

Test Steps:

  1. Send a Create Purchases request with items that have active promotions
  2. Verify discounts are applied correctly

Expected Result: HTTP 201; purchaseId returned; promotions applied

4.3 Empty Cart Handling

Test Case ID: VAL-OP-003 Objective: Verify empty cart returns empty purchaseId

Test Steps:

  1. Send a Create Purchases request with cartItems: []
  2. Verify empty purchaseId is returned

Expected Result: HTTP 201; purchaseId: ""

4.4 Idempotency

Test Case ID: VAL-OP-004 Objective: Verify duplicate requests return the same purchaseId

Test Steps:

  1. Send a Create Purchases request
  2. Send the same request again with the same idempotentShoppingTripId

Expected Result: Same purchaseId returned; no duplicate records

5. Payment Lifecycle Validation

5.1 Successful Adjust → Capture Flow

Test Case ID: VAL-PAY-001 Objective: Verify the happy path payment flow

Test Steps:

  1. Complete a shopping trip with items
  2. Call Adjust Charge → verify APPROVED
  3. Call Capture Charge → verify HTTP 200

Expected Result: Full payment lifecycle completes successfully

5.2 Empty Cart → Cancel Flow

Test Case ID: VAL-PAY-002 Objective: Verify empty cart triggers cancellation

Test Steps:

  1. Complete a shopping trip with no items
  2. Call Cancel Charge → verify HTTP 200

Expected Result: Pre-auth cancelled; no charge

5.3 Declined Adjust — Bad Debt Recording

Test Case ID: VAL-PAY-003 Objective: Verify declined adjustment is handled correctly

Test Steps:

  1. Trigger a declined adjustment
  2. Verify bad debt is recorded
  3. Verify Report Payment Status is called with settledAmount: 0

Expected Result: Bad debt recorded; payment feedback sent to Amazon

5.4 Successful Refund

Test Case ID: VAL-PAY-004 Objective: Verify refund processing works

Test Steps:

  1. Complete a full payment lifecycle (adjust → capture)
  2. Call Refund API with a valid reason code
  3. Verify reconciliationId returned

Expected Result: HTTP 200; refund processed

6. End-to-End Flow Validation

6.1 Complete Shopping Journey — App Entry

Test Case ID: VAL-E2E-001 Objective: Validate the full shopper journey via app entry

Test Steps:

  1. Shopper scans QR code at gate
  2. Verify Identity Keys returns VALID → gate opens
  3. Shopper picks up items and exits
  4. Amazon sends cart → Create Purchases returns purchaseId
  5. Partner calls Adjust Charge → APPROVED
  6. Partner calls Capture Charge → success
  7. Receipt generated and delivered

Expected Result: Seamless end-to-end flow via app entry

6.2 Complete Shopping Journey — Credit Card Entry

Test Case ID: VAL-E2E-002 Objective: Validate the full shopper journey via credit card entry

Test Steps:

  1. Shopper taps credit card at gate
  2. F&A Connector returns APPROVED → gate opens
  3. Shopper picks up items and exits
  4. Amazon sends cart → Create Purchases returns purchaseId
  5. Partner calls Adjust Charge → APPROVED
  6. Partner calls Capture Charge → success
  7. Receipt generated and delivered

Expected Result: Seamless end-to-end flow via credit card entry

6.3 Empty Cart Journey (Both Entry Methods)

Test Case ID: VAL-E2E-003 Objective: Validate empty cart flow for both entry methods

Test Steps:

  1. Test empty cart via app entry → Cancel Charge → no charge
  2. Test empty cart via credit card entry → Cancel Charge → no charge

Expected Result: Pre-auth released for both entry methods

6.4 Bad Debt → Entry Denial → Resolution (Credit Card)

Test Case ID: VAL-E2E-004 Objective: Validate the bad debt lifecycle for credit card entry

Test Steps:

  1. Trigger a declined adjustment → bad debt recorded
  2. Report Payment Status sent to Amazon
  3. Shopper returns via credit card → F&A Connector denies entry
  4. Shopper resolves debt → Report Payment Status with full settlement
  5. Shopper returns → F&A Connector approves entry

Expected Result: Full bad debt lifecycle works correctly

7. Configuration Validation Checklist

Configuration Validated Notes
Verify Identity Keys API allowlisted ☐  
F&A Connector ARN allowlisted ☐  
F&A Connector configured in Merchant Portal ☐  
F&A Connector connectivity test passed ☐  
Ordering Connector ARN allowlisted ☐  
Ordering Connector configured in Merchant Portal ☐  
Ordering Connector connectivity test passed ☐  
Payment Service APIs allowlisted ☐  
Refund API allowlisted ☐  
Report Payment Status API allowlisted ☐  
Get Transactional Data API allowlisted ☐  
Get Shopper Identity API allowlisted ☐  
Payment processor configured ☐  
Store ID correctly mapped ☐  
Catalog uploaded and active ☐  
QR code scanning configured (app entry) ☐  
Follow us:
amazon_developer_logo

© 2010-2026, Amazon.com, Inc. or its affiliates. All Rights Reserved.

Terms

Amazon Developer Blog

Contact Us