> ## 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.

# Usage and configuration

> Add the Deuna node to your Canvas flow, configure the payment method, and test external confirmation payments.

Once the integration is connected, the **Deuna** node is available in Canvas. The user completes payment in the **Deuna app** (redirect or unique code) and the flow continues when Deuna confirms the result.

> [!TIP]
>
> If you have not installed the integration yet, start with [Connect in Brain Studio](https://docs.jelou.ai/guides/integraciones/pagos/proveedores/deuna/conectar-en-brain-studio.md).

***

## Add the node to Canvas

**1. Open your flow in Canvas**

Open in Brain Studio the flow where you want to add Deuna payments.

**2. Add the Deuna node**

Add **Deuna** from the **Canvas** toolbar, the **Payments** node, or from available payment providers once the integration is installed.

The exact location may vary depending on whether you started installation from Marketplace, Jelou Agent, the payments node in Canvas, or a template.

**3. Connect the node at the charge point**

Connect the Deuna node after the flow already has the amount and purchase confirmation.

**4. Open the configuration panel**

Select the node to open the right-side panel. Complete the **Payment data** and **Advanced** tabs, and review the **outputs** available on the Canvas node.

If required fields are missing, the node shows *Incomplete configuration. Check the node fields.* and the environment badge (**Development** or **Production**).

***

## Configure the node

> [tab] Payment data
>
> > [accordion] Personalization
> >
> > **Personalization** `boolean` (default: false)
> >
> > Enable it to define the messages that accompany your payment button.
> >
> > When active, it enables **Header**, **Body**, and **Footer** fields.
>
> > [accordion] Header
> >
> > **Header** `string`
> >
> > Title of the payment button message.
> >
> > Shown when **Personalization** is active.
>
> > [accordion] Body
> >
> > **Body** `string`
> >
> > Main text of the payment button message.
> >
> > Shown when **Personalization** is active.
>
> > [accordion] Footer
> >
> > **Footer** `string`
> >
> > Closing text of the payment button message.
> >
> > Shown when **Personalization** is active.
>
> > [accordion] Payment method
> >
> > **Payment method** `string` *required*
> >
> > Defines how the user starts payment in Deuna. Available options:
> >
> > * **Redirect to app** — the message includes a button that opens the Deuna app to complete payment.
> > * **Unique code** — Brain Studio generates a code the user must **copy and paste into the Deuna app** to pay.
> >
> > In both cases payment is completed **outside WhatsApp**. The flow continues when Deuna confirms the result.
> >
> > ![Deuna node with Redirect to app payment method selected in Payment data](https://mintcdn.com/jelouai/3D3ye1Wdwh66cTgk/assets/images/integraciones/pagos/deuna-nodo-forma-pago-redireccion.png?fit=max\&auto=format\&n=3D3ye1Wdwh66cTgk\&q=85\&s=52977c1dd090f40efaba50fff3e1604f)
> >
> > Payment method: Redirect to app
> >
> > ![Deuna node with Unique code payment method selected in Payment data](https://mintcdn.com/jelouai/3D3ye1Wdwh66cTgk/assets/images/integraciones/pagos/deuna-nodo-forma-pago-codigo.png?fit=max\&auto=format\&n=3D3ye1Wdwh66cTgk\&q=85\&s=aace51863dffd4559a3d8968ccb200f7)
> >
> > Payment method: Unique code
> >
> > > [!TIP]
> > >
> > > Use **Redirect to app** to minimize manual steps. Use **Unique code** when users are familiar with pasting codes in Deuna or when your flow requires it.
>
> > [accordion] Payment reason
> >
> > **Payment reason** `string` *required*
> >
> > Descriptive text for the charge. Examples: order number, product, service, or internal reference.
>
> > [accordion] Taxable amount
> >
> > **Taxable amount** `number` *required*
> >
> > Amount subject to VAT. Numbers only, in US dollars (USD).
>
> > [accordion] Tax-free amount
> >
> > **Tax-free amount** `number` *required*
> >
> > Tax-exempt amount. Numbers only. If not applicable, use `0`.

> [tab] Advanced
>
> ![Deuna node with Advanced tab open showing environment, USD currency, and VAT](https://mintcdn.com/jelouai/3D3ye1Wdwh66cTgk/assets/images/integraciones/pagos/deuna-nodo-avanzado.png?fit=max\&auto=format\&n=3D3ye1Wdwh66cTgk\&q=85\&s=0590eb3effe773bfa981a755a14328ab)
>
> Advanced tab: environment, expiration, currency, and VAT
>
> > [accordion] Environment
> >
> > Shows whether Deuna operates in **Development** or **Production**.
> >
> > In **Development**, you will see *Your integration is in development mode. Move it to production when you are ready.* and can start **Go to production**.
> >
> > > [!NOTE]
> > >
> > > **Development** corresponds to an installation with **test credentials**. **Production** corresponds to **production credentials**.
>
> > [accordion] Payment button expiration
> >
> > **Payment button expiration** `string`
> >
> > Defines how long the payment button or code remains valid after it is sent.
> >
> > Select an option from the list available in Brain Studio.
>
> > [accordion] Currency
> >
> > **Currency** `string` *required*
> >
> > Charge currency. For Deuna in Ecuador, the value is **USD**.
>
> > [accordion] VAT percentage
> >
> > **VAT percentage** `number`
> >
> > VAT percentage applied to the operation.
> >
> > Must be consistent with **applied VAT** configured during installation in [Connect in Brain Studio](https://docs.jelou.ai/guides/integraciones/pagos/proveedores/deuna/conectar-en-brain-studio.md).
>
> > [accordion] Payment metadata
> >
> > **Payment metadata** `string`
> >
> > Optional field for internal reference such as order ID, correlator, or user ID.

***

## Node outputs

Outputs appear on the Deuna node in Canvas. Connect them based on the result you want to handle in your flow.

> [accordion] Successful payment
>
> Triggered when Deuna confirms the transaction was approved.
>
> Recommendations:
>
> * confirm the order
> * send receipt or notification
> * update purchase status in your systems

> [accordion] Pending payment
>
> Triggered when the transaction is in process or awaiting confirmation in the Deuna app.
>
> Recommendations:
>
> * inform the user clearly
> * indicate they must complete payment in Deuna (app or code)
> * avoid creating a second charge while the status is unresolved

> [accordion] Payment message sent
>
> Triggered when the payment button message or unique code is sent successfully in the conversation.
>
> This output **does not** confirm payment. It only indicates the user received the CTA (redirect or code) and can continue in the Deuna app.
>
> You can connect this output to a **post-send payment message support AI Agent** to assist the user while they complete payment outside WhatsApp.
>
> **Recommendations:**
>
> * explain how to open the app or paste the code in Deuna
> * answer questions while waiting for provider confirmation
> * do not confirm payments from this output
>
> **Reference prompt example:**
>
> ```txt theme={null}
> Act as brief support after the user received a Deuna charge in WhatsApp.
>
> Context:
> Payment completes in the Deuna app (redirect or unique code). Your role is to answer questions before Deuna confirms the result.
>
> Rules:
> - Do not confirm payments or invent statuses
> - Do not generate new codes or new charges
> - For redirect: tell the user to open the button and follow steps in Deuna
> - For unique code: tell the user to paste the code in Deuna and wait for confirmation
> - If they say they already paid: ask them to wait for confirmation in the chat
> - Keep responses brief and clear
> ```

> [accordion] Failed payment
>
> Triggered when the transaction was rejected, declined, or not completed.
>
> Recommendations:
>
> * allow a controlled retry
> * offer support or an alternate path

> [accordion] Error
>
> Triggered on technical errors, provider errors, or communication failures during payment creation or processing.
>
> Recommendations:
>
> * log the error
> * show a contingency message
> * retry in a controlled way and escalate if it persists

***

## Test payments

If Deuna is connected with **test credentials**, validate the flow before going to production.

> [!NOTE]
>
> In test mode, verify the node shows **Development** in the **Advanced** tab. Payment completes in the Deuna app; the WhatsApp flow continues when Deuna notifies the result.

**1. Confirm test credentials**

Verify Deuna was installed with **test credentials** (development Api key, Api secret, and merchant code).

**2. Choose Payment method**

In **Payment data**, select **Redirect to app** or **Unique code** depending on the scenario you want to test.

**3. Test from WhatsApp**

Trigger the flow from WhatsApp. With redirect, open the Deuna app from the button. With unique code, paste the code in the Deuna app.

**4. Validate flow output**

Verify which output the flow continues through:

* **Payment message sent** (CTA send only)
* **Successful payment**
* **Pending payment**
* **Failed payment**
* **Error**

***

## Go to production

If you installed Deuna with **test credentials**, you can start going to production from the Deuna node's **Advanced** tab in **Canvas** or from the **Deuna** page in **Marketplace**.

You must enter production **Api key**, **Api secret**, and **merchant code**. Details in [Connect in Brain Studio — Go to production](https://docs.jelou.ai/guides/integraciones/pagos/proveedores/deuna/conectar-en-brain-studio.md#go-to-production).

Before operating with real payments:

* Make sure you have **production credentials** from Deuna.
* Confirm **VAT percentage** and **Currency (USD)** on the node match your operation.
* Remember the **\$0.10 USD** cost per production transaction.
* Run a low-amount real payment test before scaling.

***

## Important considerations

> [accordion] External confirmation
>
> Deuna does not use an embedded WebView in WhatsApp. The user pays in the **Deuna app**. Your flow must handle **Payment message sent**, **Pending payment**, and final outputs without assuming immediate confirmation.

> [accordion] Redirect vs unique code
>
> **Redirect to app** opens Deuna directly. **Unique code** requires the user to copy and paste the code. Choose based on your audience and flow copy.

> [accordion] Environment and credentials
>
> Test and production credentials are different. Node environment (**Development** / **Production**) must match credentials used at installation or when going to production.

> [accordion] Pending payments
>
> After sending the CTA, payment may remain pending until the user acts in Deuna. Inform clearly and avoid a second charge until the status is resolved.

***

## Next step

> [card] [Coverage and pricing](https://docs.jelou.ai/guides/integraciones/pagos/proveedores/deuna/cobertura-y-precios.md)
>
> Review availability, payment methods, and Deuna reference fees.


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