Confirming an Allocation (3DS)
When a payment allocation requires 3D Secure (3DS) authentication, it enters either the AUTHREQUIRED or CONFIRMATIONREQUIRED status. The customer must complete the 3DS challenge in their browser or app before the allocation can proceed. Once the challenge is complete, the checkout flow calls the Confirm Allocation endpoint to continue the payment flow for that specific allocation.
Backward Compatibility
Backward compatibility is a one-directional bridge that enables v2 API endpoints to operate seamlessly on v1-origin payment and refund resources. This eliminates operational gaps during migration by allowing in-flight v1 resources to be managed through v2 APIs without requiring a hard migration window.