Exploration Guide
Learn payment journeys hands-on. Run real requests, complete checkout with SDK, inspect status transitions, and validate webhook behavior in one place.
Popular Flows
Start here to explore core card journeys.
CIT with 0 amount Authorization
Validate and tokenize a customer card with a 0 amount authorization for customer-initiated usage. Create the customer first, run the zero-auth payment, then retrieve and store customer_id + payment_method_id.
CIT - Direct Subscription
Create a customer and process a non-zero customer-initiated payment to establish saved payment artifacts for subscription onboarding. This is the direct-subscription counterpart to CIT zero-auth.
MIT with PSP Token
S2S-only journey. Recap CIT setup to retrieve and store payment_method_id, then execute MIT charges using customer_id + payment_method_id.
Manual Captures
Authorize first and capture later. Use this when fulfillment happens after checkout and you only want to settle funds once ready.
Partial Captures
Authorize once and capture in multiple portions over time. Useful when fulfillment happens in phases.
Overcaptures
Authorize an initial amount and capture a higher amount later when overcapture is enabled.
Save Card (New User)
Save a card during the first purchase for a brand new customer. Creates the customer record and saves their payment method in a single flow. Ideal for account creation with payment.
Returning User (Saved Card)
Process a customer-present payment for an existing customer using previously saved cards. This is the returning-user continuation after card-on-file setup.
Guest Customer Journey
Run a non-3DS guest payment without customer_id. Supports both SDK and S2S paths while keeping the flow minimal.
Payments via PM (Card)
Tokenize cards as Payment Methods first, then charge later using payment_token (SDK PM session) or by mapping S2S payment_method_id into payment_token.