Change Details

This is a diagram of our end-to-end credit card payment submission via Gravy. **Covers**: - Page load and checkout session creation - Secure Fields iframe rendering - Form submission - Two-phase fraud filtering (pre-auth and post-auth), - Authorisation call via SmashPig to the Gravy API - 3DS redirect handling - Fraud REVIEW path (authorised but not captured), - Capture call via SmashPig to the Gravy API - Queue message creation (payments-antifraud, pending, donations). **Notes**: - The edge cases are disruptive but important to capture. - I didn't go into great detail about the client-side JavaScript flow. We could add that too for visibility. {F72316825, size=full}

This is a diagram of our end-to-end credit card payment submission via Gravy. **Covers**: - Page load and checkout session creation - Secure Fields iframe rendering - Form submission - Two-phase fraud filtering (pre-auth and post-auth), - Authorisation call via SmashPig to the Gravy API - 3DS redirect handling - Fraud REVIEW path (authorised but not captured), - Capture call via SmashPig to the Gravy API - Queue message creation (payments-antifraud, pending, donations). **Notes**: - The edge cases are disruptive but important to capture. - I didn't go into great detail about the client-side JavaScript flow. We could add that too for visibility.

This is a diagram of our end-to-end credit card payment submission via Gravy. **Covers**: - Page load and checkout session creation - Secure Fields iframe rendering - Form submission - Two-phase fraud filtering (pre-auth and post-auth), - Authorisation call via SmashPig to the Gravy API - 3DS redirect handling - Fraud REVIEW path (authorised but not captured), - Capture call via SmashPig to the Gravy API - Queue message creation (payments-antifraud, pending, donations). **Notes**: - The edge cases are disruptive but important to capture. - I didn't go into great detail about the client-side JavaScript flow. We could add that too for visibility. {F72316825, size=full}