payment.createdA payment request has entered the payment flow.
DEVELOPER EVENT SYSTEM
Payment Infrastructure for Developers
Architecture guidance for gaming payment events, webhook logic, status confirmation, testing, idempotency, and merchant-side order state. Examples are conceptual, not production API documentation.
> event.payment.created> webhook.verify> order.state.confirmedConceptual event documentation
payment.pendingThe payment has not reached a final state.
payment.confirmedThe payment has received a verified successful status according to the provider flow.
payment.failedThe payment did not complete successfully.
Actual event names and payload structures depend on the payment provider API.
Webhook lifecycle
PROVIDER EVENT
SIGNATURE OR AUTH CHECK
IDEMPOTENCY CHECK
STATUS VERIFY
ORDER UPDATE
BALANCE LOGIC
Recommended merchant-side logic
Idempotency concepts
Design this behavior explicitly and align it with the provider's documented integration flow before production use.
Server-side confirmation
Design this behavior explicitly and align it with the provider's documented integration flow before production use.
Event logging
Design this behavior explicitly and align it with the provider's documented integration flow before production use.
Duplicate callbacks
Design this behavior explicitly and align it with the provider's documented integration flow before production use.
Order state separation
Design this behavior explicitly and align it with the provider's documented integration flow before production use.
Player balance updates
Design this behavior explicitly and align it with the provider's documented integration flow before production use.