> ## Documentation Index
> Fetch the complete documentation index at: https://docs.jelou.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Test a gateway before publishing it

> Use the test checkout to validate the full flow before activating your custom gateway in production.

When your gateway has credentials connected (the wizard's **Connect** step), **Payments → Integrations** shows a **Test** action. It opens the test checkout panel so you can validate the full cycle before production.

## How to test

**1. Fill in the test data**

Enter order and customer data: name, phone, reference id, amounts, tax, and currency. Optional fields only appear if your body template or headers use them.

![Test checkout panel of a custom gateway, with name, phone, amount, and currency fields](https://mintcdn.com/jelouai/R4qL5d7Hj6fxJl87/assets/images/integraciones/pagos/personalizadas/probar-checkout.png?fit=max\&auto=format\&n=R4qL5d7Hj6fxJl87\&q=85\&s=167ce88da6ed93a7a457846e1bd78a3e)

Test checkout panel, with the order and customer data

**2. Review the preview**

The panel shows live how the request looks with placeholders already replaced, before anything is sent to the PSP.

**3. Generate the test payment**

On confirm, Jelou calls your gateway and shows the resulting **paylink** with the PSP response, or an error message if it's rejected.

> [!NOTE]
>
> The test panel includes a return URL field. It does not include cancellation or channel/user identifiers.

Run this flow against the PSP's **sandbox** or test mode before going to production or using the gateway in a live Brain flow.

## Checklist before production

**1. JelouPayments credentials**

Confirm your company has JelouPayments credentials configured.

**2. Correct environment**

Validate first in **Sandbox** (or the PSP's test mode) before creating the **Production** equivalent.

**3. PSP credentials**

Every secret your PSP needs is declared, and sensitive ones are typed as **Secret**.

**4. Verified request**

The URL, method, body, payment link path, and transaction id path match the PSP's real API—verified with **Test**.

**5. Valid placeholders**

Review body, headers, and status check against the [placeholder reference](https://docs.jelou.ai/en/guides/integrations/payments/custom/variables-and-placeholders.md).

**6. Return and status (if applicable)**

If your PSP redirects after payment, the transaction id parameter matches what it adds to the URL. If you use a status check, the **Success / Failed / None** mapping is complete.

**7. Webhook (if applicable)**

Signature header configured if the PSP signs webhooks, correct payload paths, and every relevant event mapped to **Success**, **Failed**, or **None**.

**8. Shared webhook secret**

The generated or rotated secret is also configured in the PSP's dashboard.

**9. Full test checkout**

You generated a real sandbox paylink, completed a payment end to end, and the resulting status is the expected one.

**10. Production**

> [!WARNING]
>
> Production credentials can create a real charge. Use the PSP's test mode when it exists. If it doesn't, run only an authorized minimum-amount transaction and define its void or refund before continuing.

Switch to **Production**, repeat the test checkout with production credentials, and re-verify webhook signature validation end to end.

## Activation in Brain Studio

A newly created gateway **doesn't appear immediately** in the Payment node selector. Jelou verifies the configuration in the background and marks it **active** when ready. You can't force that step from the UI.

> [!NOTE]
>
> Plan some time between finishing the wizard and being able to use the gateway inside a Brain flow.

## Next steps

> [card] [Use in Brain Studio](https://docs.jelou.ai/en/guides/integrations/payments/custom/use-in-brain-studio.md)
>
> Configure the Payment node once your gateway is active.

> [card] [Create a custom gateway](https://docs.jelou.ai/en/guides/integrations/payments/custom/create-gateway.md)
>
> Go back to the wizard if you need to adjust a step.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.