Advanced Payment
The Advanced Payment action allows chatbot builders to create highly customizable payment workflows inside Ownchat using WhatsApp Payment integrations.
Unlike standard payment actions, Advanced Payment supports:
Dynamic reference IDs
Expiration controls
Tax configuration
Catalog visibility
Product-level customization
Media uploads
Static and dynamic product data
This connection action helps businesses create flexible payment experiences for both physical and digital products directly inside chatbot conversations.
The walkthrough demonstrates configuring WhatsApp Payment connections, dynamic variables, catalog settings, payment expiration, tax information, product catalogs, and payment response storage.
When to Use Advanced Payment
Use the Advanced Payment action when your chatbot requires detailed payment configuration and customizable product-based payment workflows.
Common Use Cases
E-commerce checkout
Subscription invoices
Product catalog payments
Digital product sales
Restaurant ordering systems
Multi-product billing workflows
Example Interaction
Bot: Your payment request is ready. Please complete the payment to activate your plan.
The chatbot dynamically generates an advanced payment request with configurable product and billing details.
Prerequisites
Before configuring the Advanced Payment action:
WhatsApp Payment integration must already be connected.
API responses or order variables should already exist if dynamic references are required.
The walkthrough specifically notes:
The ID is stored in the store response variable in the API action.
How to Add Advanced Payment
Follow these steps to add the Advanced Payment action to your bot workflow.
Open Bot Builder
Click the Add Node button
Open the Connections tab
Select Payments
Click Advanced Payment
Configure the payment settings
Configure catalog and product details
Configure response variables
Click Create
Click Publish to deploy the workflow
The walkthrough demonstrates selecting Advanced Payment from the Payments section.
Accessing the Connections Section
To access the Advanced Payment action:
Click Add Node
Open the action panel
Click the Connections tab
The walkthrough specifically states:
To create an advance payment in WhatsApp Payment, you need to connect the app first and proceed.
Selecting Advanced Payment
Inside the Payments section:
Locate Advanced Payment
Click the action to open the configuration panel
The walkthrough specifically notes:
Select Advanced Payment to connect it with the API call.
Advanced Payment Configuration
When configuring the Advanced Payment action, several fields must be completed.
Action Name
The Action Name identifies the payment workflow inside the bot builder.
This name is visible only within the workflow editor.
Example
Advanced Subscription Payment Premium Checkout WhatsApp Product Payment
The walkthrough demonstrates renaming the default value to:
Advance payment
before saving the configuration.
Body Text
The Body Text field contains the payment request message displayed to the customer.
Example
Awesome! We've received your details ✅ To activate your plan, please click the "Pay Now" button below.
The walkthrough demonstrates configuring a payment message with activation instructions.
Connection ID
The Connection ID field allows you to select the configured WhatsApp Payment integration.
To configure:
Open the dropdown
Select the connected payment account
The walkthrough specifically selects:
OwnchatWhatsappPay live final
from the available connections list.
Reference ID
The Reference ID field stores the order or transaction identifier associated with the payment.
To configure:
Click Add Variable
Select the API response variable
Append the required response path
The walkthrough demonstrates selecting:
id
from the stored API response variables.
The walkthrough then appends:
.data
to access the correct API response value.
Final example:
{{variables.id.data}}
Goods Type
The Goods Type field specifies the type of product or service associated with the payment.
Available options shown include:
Digital Goods
Physical Goods
Digital Goods
Used for:
Subscription plans
Software licenses
Online services
Digital downloads
Physical Goods
Used for:
Food orders
Product deliveries
Retail purchases
E-commerce items
The walkthrough specifically notes:
If a customer orders food via Petpooja, choose Physical Goods; if you send a subscription invoice, choose Digital Goods.
Expiration Data Format
The Expiration Data Format field defines the time unit for payment expiration.
Available options shown include:
Minutes
Hours
The walkthrough specifically selects:
Hours
as the expiration format.
Expiration Data Value
The Expiration Data Value field defines how long the payment request remains valid.
Example
24
The walkthrough demonstrates setting the payment expiration to 24 hours.
Expiration Description
The Expiration Description field explains the expiration condition shown to the customer.
Example
Payment link expired
The walkthrough demonstrates entering a payment expiration description.
Tax Value
The Tax Value field specifies the tax amount applied to the transaction.
Example
1799.82
The walkthrough demonstrates entering a tax amount manually.
Tax Description
The Tax Description field explains the tax details applied to the payment.
Example
18% GST
The walkthrough demonstrates configuring GST tax descriptions.
Is Catalog Available
The Is Catalog Available toggle controls whether customers can view products inside the payment workflow.
When Enabled
Products become visible to customers
Customers can browse available items
The walkthrough specifically notes:
If you enable the catalog, the items are shown in this action.
When Disabled
Products remain hidden
Customers cannot browse the catalog
The walkthrough specifically notes:
Catalog visibility is turned off, so customers cannot see or browse products.
Catalog Type
The Catalog Type field defines how product data should be managed.
Available options include:
Static
Dynamic
Static Catalog
Uses manually entered product details.
Dynamic Catalog
Automatically retrieves product information from real-time data sources.
The walkthrough specifically notes:
Static means fixed values, while Dynamic updates automatically based on real-time data.
Product Name
The Product Name field specifies the name of the product shown in the payment request.
Example
Premium Subscription
The walkthrough demonstrates manually entering product names.
Product Media Upload
The Upload Media option allows product images or media files to be attached to the payment request.
To configure:
Click Upload Media
Select the media file
Click Send Selected Files
The walkthrough demonstrates uploading product media files successfully.
Product Price
The Price field specifies the product cost.
Example
999
The walkthrough demonstrates entering product pricing manually.
Product Quantity
The Quantity field specifies the number of product units included in the payment.
Example
1
This field supports multi-product payment configurations.
Notes Section
The Notes section allows additional metadata to be attached to the payment request.
This is commonly used for:
Order IDs
Customer references
Internal tracking
Note Key
The Note Key field defines the metadata label.
Example
order_id
The walkthrough demonstrates adding multiple payment notes.
Note Value
The Note Value field contains the associated value or variable.
The walkthrough demonstrates:
Clicking Add Variable
Selecting the stored response variable
Appending:
.data to retrieve the required value.
Store Response Variable
The Store Response Variable field defines where the payment response should be stored.
The walkthrough demonstrates creating:
payment_advance
as the response storage variable.
Creating the Advanced Payment Action
After configuring all payment settings:
Review the workflow configuration
Click the Create button
The Advanced Payment node will now appear in the workflow canvas.
Workflow Behavior
Once triggered, the Advanced Payment action:
Connects with WhatsApp Payment integrations
Supports advanced product configuration
Handles catalog-based product payments
Supports expiration and tax controls
Stores payment responses dynamically
The walkthrough demonstrates configuring a complete advanced WhatsApp payment workflow using API-connected references and catalog products.
Example Workflow
Example Chatbot Workflow
Create Order via API ↓ Advanced Payment ↓ Generate Payment Request ↓ Store Payment Response ↓ Send Payment Confirmation
Example Interaction
Bot: Your payment request is ready. Plan: Premium Subscription Amount: ₹9,999 Validity: 24 Hours
The chatbot dynamically generates a complete payment request with product and tax details.
Publishing the Bot Changes
After configuring the Advanced Payment workflow:
Review all payment settings
Click the Publish button
Deploy the updated workflow to production
The walkthrough concludes by publishing the configured advanced payment workflow successfully.
Best Practices
Follow these recommendations when using Advanced Payment.
Use dynamic references for orders
Link payment requests with API-generated order IDs.
Configure catalog visibility carefully
Enable catalogs only when customers need product browsing.
Use expiration controls
Prevent outdated payment requests from remaining active.
Upload optimized product media
Use clear and properly sized product images.
Test complete payment flows before publishing
Validate product, payment, tax, and expiration configurations.
Summary
The Advanced Payment action allows chatbot builders to create fully customizable WhatsApp payment workflows inside Ownchat.
With Advanced Payment, you can:
Configure advanced payment workflows
Handle physical and digital goods
Use catalog-based product payments
Configure taxes and expiration rules
Upload product media and pricing details
Store payment responses dynamically
This connection action helps businesses create powerful commerce automation and advanced WhatsApp payment experiences within Ownchat.
Last updated