Testing and Validation
Systematic testing and validation before full-scale integration is the critical step for ensuring data quality.7.1 Small-Batch-First Strategy
Core principle: Start with approximately 100 products, confirm everything works correctly, then scale up to full volume.7.2 Required Field Validation
Ensure all required fields are correctly populated:7.3 Price Format Validation
Prices must use minor currency units (the smallest denomination):amountmust be greater than or equal to 0 (0 means free)currencyuses ISO 4217 three-letter codes- Confirm you are not passing dollars instead of cents ($99.99 USD should be
9999, not99)
7.4 URL Validation
Check every URL individually:7.5 SFTP Connection Testing
Verify SFTP connectivity before uploading production data:7.6 API Authentication Testing
Verify API credentials and header configuration:- Whether the Bearer token is correct
- Whether the token has expired
- Whether account permissions have been activated
7.7 Common Error Troubleshooting
HTTP 400: invalid_payload
Cause: Malformed request body or missing required fields.HTTP 404: not_found
Cause: The requested Feed or product does not exist.Idempotency Conflicts
If you send different request bodies using the sameIdempotency-Key, a conflict may occur. Each distinct request batch must use a unique key.
7.8 Checkout Session Testing
If the merchant also implements Agentic Checkout endpoints, the complete transaction flow must be tested.Create a Session
Update a Session
Complete Payment
Cancel a Session
7.9 Delegate Payment Testing
Stripe provides a test mode for payment integration testing:
Test mode does not generate real transactions, allowing you to safely validate the full payment flow.
7.10 Post-Launch Data Sync Monitoring
After going live, continuously monitor data synchronization:Next chapter: Chapter 8: Frequently Asked Questions — Common questions about ACP integration