Payment Journey

This interactive guide walks you through a complete payment integration with Ottu. Each step is live — you'll make real API calls to our sandbox, render the actual Checkout SDK, receive real webhook notifications, and query payment status. No real charges are made.

Payment Integration Journey

Walk through a complete Ottu payment integration with live API calls. Every step runs against our sandbox — no real charges.

What You've Learned

• Payment Methods API discovers available gateways dynamically — add or remove gateways in the control panel and they're automatically reflected.
• Checkout API creates payment sessions with a single POST call, returning a session_id and checkout_url.
• Two payment paths — redirect customers to Ottu's hosted checkout page, or embed the Checkout SDK directly on your site.
• Webhooks deliver payment results to your server in real-time — this is the primary integration mechanism.
• PG Params normalize gateway responses into consistent fields — switch gateways without changing your webhook handling code.
• Payment Status Query is your fallback when webhooks don't arrive — same response structure, same fields.

Dive Deeper

• Checkout API — Full API reference with all parameters and response fields
• Checkout SDK — SDK integration guides for Web, iOS, Android, and Flutter
• Payment Methods — Gateway discovery, filtering, and dynamic updates
• Webhooks — Setup, payload reference, and signature verification
• PG Params — Normalized gateway response fields for consistent webhook handling
• Payment Status Query — Throttling rules, automatic inquiry, and timing guidance
• Recurring Payments — Tokenization and auto-debit for saved cards
• Operations — Refund, capture, void, cancel, and expire payment transactions
• Payment States — Complete state machine reference for payment transactions and attempts