Skip to main content
Payments in Brain Studio lets you initiate, execute, and confirm charges within a conversation (for example on WhatsApp), and continue the flow based on the actual result of the transaction. The platform supports different payment experiences, depending on the provider and payment method used:
  • WebView embedded in WhatsApp, where the customer completes the checkout within the conversation.
  • Native in-chat experience, when the payment method supports it.
  • Conversational flows for wallets or transfers, when confirmation occurs outside the traditional checkout.
Jelou does not hold funds. Each implementing user uses their own account and credentials from the corresponding payment provider.

​
How it works

A payment in Brain Studio always involves three clearly separated roles:
  • 🧠 Brain Studio → Builds the request and exposes the status
  • 💳 Payment provider → Executes the transaction and settles funds
  • 🎯 Your implementation → Decides the next action based on the status received

​
Responsibilities of each party

  • Builds the request (amount, currency, metadata).
  • Triggers the operation toward the provider.
  • Receives the status and exposes it as a result.
  • Does not authorize or settle payments.

​
Statuses you must handle

The provider will always return a transaction status. Your implementation must handle it explicitly.
The payment was confirmed successfully.Your flow should normally:
  • Continue the main process.
  • Confirm to the user.
  • Record the event (if applicable).
The operation was denied or failed.Your flow should:
  • Report the error.
  • Allow retry or an alternative method.
  • Record the reason if the provider exposes it.
The payment does not yet have a final confirmation (common for cash or transfers).Your flow should:
  • Define a follow-up strategy.
  • Query the status later (polling or webhook).
  • Avoid continuing as if it were approved.
Model the payment node as a deterministic transition: request → external execution → status → next action.

​
Integration model (BYOK)

The Marketplace payment integrations work, for the most part, with BYOK (Bring Your Own Keys):
  • You connect the provider with your credentials (API keys, Access Token, or OAuth).
  • The payment is processed and settled in the merchant’s account within the provider.
  • Brain Studio orchestrates the flow and works with the returned status.
BYOK = you bring the provider account and keys. Brain Studio does not replace the provider: it integrates it.

​
Before implementing

Define the scope of your use case:
  • Country(ies) where you will operate.
  • Payment methods required (cards, transfers, cash, local methods).
  • If the merchant already uses a specific provider, start with that provider.

​
Typical implementation flow

1

Choose provider and experience

Define the country(ies), payment method(s), and the experience (WebView / native / conversational).
2

Obtain credentials

Generate credentials in the provider’s dashboard (test and/or production depending on your case).
3

Install from Marketplace (BYOK)

Install the integration and enter your credentials. The provider becomes available as a tool in Brain.
4

Use in Brain and handle statuses

Implement the payment in your flow and explicitly handle Approved / Rejected / Pending (when applicable).
The recommended practice is to treat the payment as a “status-based decision”: the provider returns a status and your flow continues on the correct branch.

​
Next steps

Tutorial: Implementing your first charge from WhatsApp

Step-by-step tutorial: from credentials to your first charge in production.

Payment experiences

When to use embedded WebView, native in-chat experience, or conversational flows.

Available providers

Providers by country, integration scope, and specific guides.