WhatsApp Payments via PIX Code
Updated
Sprinklr supports WhatsApp Payments via PIX codes for businesses operating in Brazil, enabling brands to share secure payment instructions with customers directly on WhatsApp using approved HSM Utility templates.
With this capability, businesses can generate a PIX code through a supported payment service provider and send it to customers as part of an order‑related WhatsApp message. Customers simply copy the PIX code and complete the payment securely in their banking application.
Prerequisites
Before using WhatsApp Payments with PIX, ensure the following:
Account with a Payment Service Provider (PSP):
Currently supported: CyberSource
Note: Contact your Sprinklr Account Executive (AE) to set up a CyberSource account.
An active WhatsApp Business Account
Regional Availability: This payment option is only applicable for businesses operating in Brazil.
Create a Payment Configuration
To enable Pix‑based payments, admins must create a payment configuration in Sprinklr. This configuration becomes selectable when creating payment templates in Digital Asset Management (DAM).
Follow these steps to create a payment configuration:
1. Click the New Page (+) icon to open the Launchpad.
2. Under Platform Modules, click All Settings.
3. In All Settings, search and select Payment Configuration.
4. On the Payment Configurations page, click Create Payment Config.
5. Fill in the following details:
Field | Description |
Payment Config Name | Unique name to identify the payment configuration |
Payment Type | Select PIX |
PSP Type | Select CyberSource |
Merchant ID | Merchant identifier provided by CyberSource |
Merchant Name | Registered merchant name |
Merchant Key ID | API key ID used for authentication |
Merchant Key Secret | Secret key associated with the Merchant Key ID |
Production Config | Control whether to set up this configuration for your production or testing environment (CyberSource provides these two environment options). |
6. Click Save.
This configuration is used in the payment templates.
Payment Templates
WhatsApp payments currently support the following templates:
Order Details
Order Status
These templates are created using Dynamic Assets.
Note: To create and configure WhatsApp payment templates, please contact your Sprinklr Implementation Consultant.
Customer Payment Experience
The customer receives a WhatsApp message containing order details and a dynamic Pix code.
The customer copies the Pix code from the message.
The customer pastes the Pix code into their banking application to complete the payment.
After payment completion, the business sends an Order Status message to confirm the payment.
Payment Transactions List
You can create a payment transactions list to maintain a clear track of all transactions. This provides businesses with a centralized view where all transactions are listed in one place.
To create a payment transaction list, follow these steps:
1. Open the Persona app for Entity Studio.
2. Under Standard, search for Payment Transactions List.
3. Click the three‑dot icon (⋮) and select View.
4. In the left-navigation bar, click Record Manager.
5. In the top-right corner, click Create Record Manager.
6. Configure the following sections in the Record Manager:
Details
Field | Details |
Record Manager Name | Enter a name. |
API Reference ID | This is the API reference ID. This ID is auto-populated. |
Record Manager Type | Select Standard Record Manager. |
Record Manager View | Choose how records are displayed:
|
Density | Adjust the spacing and layout density. You can choose from the following options:
|
Columns
Add columns and configure tabs for your record manager.
Field | Description |
Columns | In the Columns drop‑down, select the relevant columns. |
Sort and Filter |
|
Row level actions | Actions appear when hovering over the three‑dot icon (⋮) in the first column. |
Inline Edit | Select which columns can be edited directly within the record manager. |
Summary Bar | Displays rolled‑up summaries of selected columns at the bottom of the record manager. |
Actions
Field | Description |
Global CTA | Add call to action buttons in the header. |
Header Actions | Actions visible in the record manager header such as Refresh and Search. |
Upfront Filters | Filters displayed in the filter bar. If no filter is selected, the bar appears by default with the option to choose filters. |
7. Once done, click Save.
Supported Standard Fields
These are the standard fields you can choose to display in the payment transactions list table.
Field Name | Description |
Client Reference Id | Unique identifier provided by the client to reference the payment transaction. |
Payment Service Reference Id | Identifier assigned by the payment service provider to track the transaction. |
Transaction Amount | The monetary amount involved in the transaction. |
Transaction Currency | The currency code (for example, USD, INR) used for the transaction. |
Payment Initiation Date | Date when the payment request was initiated. |
Payment Status Update Date | Date when the payment status was last updated. |
Payment Status | Status of the payment. |
Payment Config Id | Identifier linking the transaction to a specific payment configuration. |
Payment Type | Type of payment method used. |
Payment Service Provider Type | Type of the payment service provider (PSP) handling the transaction. |
Payer Email Id | Email address of the payer associated with the transaction. |
Reconciliation Id | Identifier used for reconciliation of payments in financial records. |