On this page
Current gateways
The current payment component exposes two gateway paths: Cashfree for INR checkout and Cryptomus for the crypto path.
| Gateway | Use | Current behavior |
|---|---|---|
| Cashfree | INR | Create payment session → open hosted checkout → verify order/payment status. |
| Cryptomus | Crypto | Create payment → receive payment URL → redirect to gateway → process signed webhook. |
Cashfree
- 01Validate project data and the refund-policy acknowledgement.
- 02Send the project payload to the Cashfree order-creation backend endpoint.
- 03Receive an order ID and payment session ID.
- 04Open Cashfree checkout with the returned payment session.
- 05Verify the order/payment state and only then show the success or failure result.
Cryptomus
- 01Validate the same project information required by checkout.
- 02Send the project payload to the Cryptomus creation backend endpoint.
- 03Store the GGX order ID for the active payment flow.
- 04Redirect the customer to the returned payment URL.
- 05The 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.
GET /api/orders/:orderId/status paymentStatus === "paid" ↓ verified order state ↓ FORGE success stateThe 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.