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

Credit Card Entry Store Validation Plan

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 Credit Card Entry Store Test Plan to validate that the partner's integration is correctly configured and functioning for a specific store deployment.

Use this plan when:

  • A partner (e.g., Daemon, Oracle Symphony, Shopify, retailcloud) has already built the integration
  • The store is being onboarded using an existing partner solution
  • You need to confirm connectivity, configuration, and end-to-end flow correctness without re-testing the full build

APIs Under Validation

API Endpoint Validation Focus
Shopper Authorization POST /v1/fraudandabuse/shopperauthorization Connectivity, APPROVED/DENIED responses
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 Shopper Authorization Connector Reachable

Test Case ID: VAL-CONN-001 Objective: Verify Amazon can invoke the partner's Shopper Authorization Connector

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.2 Ordering Connector Reachable

Test Case ID: VAL-CONN-002 Objective: Verify Amazon can invoke the partner's Ordering Connector (Create Purchases API)

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.3 Payment Service APIs Reachable

Test Case ID: VAL-CONN-003 Objective: Verify the partner can invoke Amazon's Payment Service APIs (Adjust, Cancel, Capture)

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.4 Refund API Reachable

Test Case ID: VAL-CONN-004 Objective: Verify the partner can invoke the Refund API

Test Steps:

  1. Call POST /v1/refund 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 Report Payment Status API Reachable

Test Case ID: VAL-CONN-005 Objective: Verify the partner can invoke the Report Payment Status API

Test Steps:

  1. Call POST /v1/feedback/payment-status with test data
  2. Verify HTTP 200 response (or expected 400 for test data)

Expected Result: API responds without authentication or network errors

1.6 Get Transactional Data API Reachable

Test Case ID: VAL-CONN-006 Objective: Verify the partner can invoke the Get Transactional Data API

Test Steps:

  1. Call POST /v1/payment/transactional-data with a valid test shoppingTripId
  2. Verify HTTP 200 response

Expected Result: API responds with transactional data payload

1.7 Get Shopper Identity API Reachable

Test Case ID: VAL-CONN-007 Objective: Verify the partner can invoke the Get Shopper Identity API

Test Steps:

  1. Call POST /v1/identity/shopper with a valid test shopperId
  2. Verify HTTP 200 response

Expected Result: API responds with shopper email

2. Shopper Authorization Validation

2.1 Approve Low-Risk Shopper

Test Case ID: VAL-FA-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

2.2 Deny High-Risk Shopper (Bad Debt)

Test Case ID: VAL-FA-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

2.3 Handle All Authentication Event Types

Test Case ID: VAL-FA-003 Objective: Verify the connector handles CREDIT_CARD event type without errors

Test Steps:

  1. Send a Shopper Authorization request with gateAuthenticationEvent.type: CREDIT_CARD
  2. Verify a valid authorization response is returned

Expected Result: HTTP 200 with valid shopperAuthorized decision

3. Charge Calculation Validation (Create Purchases)

3.1 Single Item Cart — Correct Pricing

Test Case ID: VAL-OP-001 Objective: Verify the partner's Ordering Connector returns correct pricing for a single item

Test Steps:

  1. Send a Create Purchases request with one known-price item
  2. Verify purchaseId is returned
  3. Verify the calculated price matches the expected catalog price

Expected Result: HTTP 201; purchaseId returned; price correct

3.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

3.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: ""

3.4 Tax Calculation

Test Case ID: VAL-OP-004 Objective: Verify tax is calculated correctly for the store's jurisdiction

Test Steps:

  1. Send a Create Purchases request with taxable items
  2. Verify tax amount matches expected rate for the store location

Expected Result: HTTP 201; tax calculated correctly

3.5 Idempotency

Test Case ID: VAL-OP-005 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
  3. Verify both return the same purchaseId

Expected Result: Same purchaseId returned; no duplicate records

4. Payment Lifecycle Validation

4.1 Successful Adjust → Capture Flow

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

Test Steps:

  1. Complete a shopping trip with items
  2. Verify Create Purchases returns purchaseId
  3. Call Adjust Charge → verify APPROVED
  4. Call Capture Charge → verify HTTP 200

Expected Result: Full payment lifecycle completes successfully

4.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. Verify Create Purchases returns empty purchaseId
  3. Call Cancel Charge → verify HTTP 200

Expected Result: Pre-auth cancelled; no charge

4.3 Declined Adjust — Bad Debt Recording

Test Case ID: VAL-PAY-003 Objective: Verify the partner handles a declined adjustment correctly

Test Steps:

  1. Trigger a declined adjustment (use test card configured for decline)
  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

4.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

4.5 Capture Amount Matches Adjust Amount

Test Case ID: VAL-PAY-005 Objective: Verify capture amount equals the authorized amount from adjust

Test Steps:

  1. Call Adjust Charge → note authorizedAmount
  2. Call Capture Charge with the same amount
  3. Verify success

Expected Result: Capture succeeds with matching amount

5. Data Retrieval Validation

5.1 Get Transactional Data After Capture

Test Case ID: VAL-DATA-001 Objective: Verify transactional data is available after capture

Test Steps:

  1. Complete a full payment lifecycle
  2. Call Get Transactional Data
  3. Verify EMV fields are present (brand, posEntryMode, tail, reconciliationId)

Expected Result: HTTP 200; all expected fields populated

5.2 Get Shopper Identity

Test Case ID: VAL-DATA-002 Objective: Verify shopper email is retrievable

Test Steps:

  1. Call Get Shopper Identity with a valid shopperId
  2. Verify shopperEmail is returned

Expected Result: HTTP 200; valid email returned

6. Error Handling Validation

6.1 Invalid Shopping Trip ID

Test Case ID: VAL-ERR-001 Objective: Verify 400 error handling for invalid shoppingTripId

Test Steps:

  1. Call Adjust Charge with an invalid shoppingTripId
  2. Verify HTTP 400 UnknownShoppingTrip

Expected Result: HTTP 400; error handled gracefully (no crash, appropriate logging)

6.2 Rate Limit Handling

Test Case ID: VAL-ERR-002 Objective: Verify the partner handles 429 responses correctly

Test Steps:

  1. Trigger a 429 response (or simulate)
  2. Verify the system retries after the Retry-After period

Expected Result: System retries with backoff; no data loss

6.3 Server Error Retry

Test Case ID: VAL-ERR-003 Objective: Verify the partner retries on 500/503 errors

Test Steps:

  1. Trigger a transient 500 error (or simulate)
  2. Verify the system retries with exponential backoff

Expected Result: Retry succeeds; no duplicate operations

7. End-to-End Flow Validation

7.1 Complete Shopping Journey — Credit Card Entry

Test Case ID: VAL-E2E-001 Objective: Validate the full shopper journey from entry to receipt

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 with correct pricing
  5. Partner calls Adjust Charge → APPROVED
  6. Partner calls Capture Charge → success
  7. Partner calls Get Transactional Data → EMV data retrieved
  8. Partner calls Get Shopper Identity → email retrieved
  9. Receipt generated and delivered

Expected Result: Seamless end-to-end flow; receipt delivered with correct data

7.2 Empty Cart Journey

Test Case ID: VAL-E2E-002 Objective: Validate the empty cart flow

Test Steps:

  1. Shopper enters store and exits without items
  2. Amazon sends empty cart → Create Purchases returns empty purchaseId
  3. Partner calls Cancel Charge → success
  4. No charge on shopper's card

Expected Result: Pre-auth released; no charge

7.3 Bad Debt → Entry Denial → Resolution

Test Case ID: VAL-E2E-003 Objective: Validate the bad debt lifecycle

Test Steps:

  1. Trigger a declined adjustment → bad debt recorded
  2. Report Payment Status sent to Amazon (settledAmount: 0)
  3. Shopper returns → F&A Connector denies entry (shopperRisks: BadDebt)
  4. Shopper resolves debt
  5. Report Payment Status sent with full settlement
  6. Shopper returns → F&A Connector approves entry

Expected Result: Full bad debt lifecycle works correctly

8. Configuration Validation Checklist

Configuration Validated Notes
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 ☐  
Follow us:
amazon_developer_logo

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

Terms

Amazon Developer Blog

Contact Us