Loading
GGX_LABS
Skip to content
> FORGE / PAYMENTS

Payment flow

How the current FORGE checkout creates, opens, and verifies payments, and what is changing.

On this page

Current gateways

The current payment component exposes two gateway paths: Cashfree for INR checkout and Cryptomus for the crypto path.

GatewayUseCurrent behavior
CashfreeINRCreate payment session → open hosted checkout → verify order/payment status.
CryptomusCryptoCreate payment → receive payment URL → redirect to gateway → process signed webhook.

Cashfree

  1. 01

    Validate project data and the refund-policy acknowledgement.

  2. 02

    Send the project payload to the Cashfree order-creation backend endpoint.

  3. 03

    Receive an order ID and payment session ID.

  4. 04

    Open Cashfree checkout with the returned payment session.

  5. 05

    Verify the order/payment state and only then show the success or failure result.

Cryptomus

  1. 01

    Validate the same project information required by checkout.

  2. 02

    Send the project payload to the Cryptomus creation backend endpoint.

  3. 03

    Store the GGX order ID for the active payment flow.

  4. 04

    Redirect the customer to the returned payment URL.

  5. 05

    The backend processes the signed webhook and checks order identity, amount, currency, and final payment state before fulfillment.

Verification

The frontend does not rely only on the browser checkout result. It requests the backend order state and checks payment status before treating the order as paid.

HTTP
POST /api/orders/:orderId/status paymentStatus === "paid" ↓ verified order state ↓ FORGE success state

The backend also validates payment amount and currency before fulfillment. Gateway webhooks are signature-verified before being processed.

Payment development

Under development
GGX Labs is adding a better payment gateway and improving the FORGE checkout experience. The current Cashfree and Cryptomus behavior is documented because it reflects the present source, but gateway selection, checkout UX, callback handling, and verification details may change.

When the new payment flow becomes the production source of truth, this article will be updated with its supported methods and final integration behavior.

Something missing or unclear?

Tell us what to improve on this page.

Send feedback