Flows + UX Patterns
ACP instant checkout enables purchases to complete within a single conversation, without leaving ChatGPT.
Checkout Flow Patterns
Pattern 1: Direct Purchase
User: "I want to buy those running shoes"
ChatGPT:
- Calls
search_products tool
- Finds matching products
- Calls
initiate_checkout tool
- Presents purchase summary
- User confirms → Purchase completes
User: "Show me running shoes under $150"
ChatGPT:
- Calls
search_products with filters
- Presents options to user
- User selects →
initiate_checkout called
- Purchase completes
Pattern 3: Reorder
User: "Reorder my last purchase"
ChatGPT:
- Calls
get_order_history tool
- Retrieves last order
- Calls
initiate_checkout with saved items
- Purchase completes
Failure States
Payment Failure
Scenario: Payment method fails
Handling:
{
"error": {
"code": "payment_failed",
"message": "Payment method declined. Please try another payment method.",
"retryable": true
}
}
ChatGPT should:
- Inform user of failure
- Offer to retry with same method
- Suggest alternative payment methods
Inventory Issues
Scenario: Product becomes unavailable
Handling:
{
"error": {
"code": "out_of_stock",
"message": "Product no longer available",
"alternatives": [
{
"id": "prod_456",
"name": "Similar Product"
}
]
}
}
ChatGPT should:
- Inform user product unavailable
- Suggest alternatives if available
- Offer to waitlist if applicable
Shipping Problems
Scenario: Shipping address invalid
Handling:
{
"error": {
"code": "invalid_address",
"message": "Shipping address could not be validated",
"fields": ["zip"]
}
}
ChatGPT should:
- Request address correction
- Validate new address
- Proceed with checkout
Security Considerations
Authentication
- Verify user identity via OpenAI accounts
- Authenticate merchant API calls
- Use secure token exchange
Payment Security
- Never store full payment details
- Use tokenized payment methods
- Comply with PCI-DSS requirements
- Implement fraud detection
Rate Limiting
- Limit checkout attempts per user
- Monitor for suspicious patterns
- Require additional verification when needed
UX Best Practices
1. Clear Purchase Summaries
Always show:
- Product details (name, variant, price)
- Shipping address
- Payment method
- Total cost
- Estimated delivery
2. Explicit Confirmation
Require clear user consent:
- "Confirm purchase?" prompts
- "Yes/No" options
- No ambiguous language
3. Error Recovery
Provide clear paths to resolve errors:
- Retry options
- Alternative suggestions
- Support contact information
Implementation Checklist
Next Steps