created
A payment request exists before a final payment outcome.
PAYMENT FLOW ENGINE
iGaming Payment Processing India
Build a payment lifecycle for gaming transactions: initiate deposits, create payment requests, track states, confirm outcomes, and handle failed or refunded transactions without relying on unsupported assumptions.
deposit initiationrequest createdpendingconfirmed / failedoperation logged
Gaming transactions do not behave like standard ecommerce orders
Gaming payment processing often involves higher event frequency, player balance sensitivity, fast support expectations, and strict separation between deposit initiation and verified confirmation. A merchant system needs visibility into pending, failed, expired, and refunded states, not just successful checkouts.
Approval, availability, and settlement behavior depend on provider rules, merchant eligibility, business model, and applicable requirements.
createdpendingconfirmedfailedexpiredrefunded
Payment state architecture
pending
The payment flow has started but no final state has been received.
confirmed
A verified successful status has been received according to the provider flow.
failed
The transaction did not complete successfully and should not credit balance.
expired
The payment window closed without a final successful confirmation.
refunded
A refund process has been requested or completed under provider rules.
Exact status models vary by provider. Merchant systems should follow documented provider states and verification procedures.