¶ Introduction
This documentation outlines the payment configuration interface, its components, and how to effectively set up different payment scenarios. The interface allows for free payment, simple fixed payments and complex dynamic payment structures based on form conditions.
¶ Basic Payment Settings
¶ Payment Type
The payment type configuration determines whether a service requires payment.
- Free: No payment is required. All payment configurations are disabled.
- Paid: Requires full payment configuration setup
¶ Payment Expiration Time
- Defined in hours
- After this period, the payment request expires and user needs to re-apply
Example:
Setting expiration to 24 hours means users have one full day to complete their payment before the request expires.
¶ Understanding Price Configuration
The price configuration panel offers two modes, controlled by toggle buttons at the top:
- Fixed
- Dynamic
¶ Fixed Pricing
One price regardless of conditions
When "Fixed" is selected, the interface shows:
- A single price input field
- Currency selector dropdown
- Example: If all visitors pay 10,000 RWF regardless of age
¶ Dynamic Pricing
Allows different prices based on form conditions and user inputs.
Selecting "Dynamic" enables a scenario-based interface:
Dynamic pricing is be based on the following:
¶ Payment Account Identifier Configuration
¶ Fixed Account
A single payment account for all transactions.
Use Cases:
- Single account for all transactions
- Use when all payments go to the same account
¶ Dynamic Account Identifier
Multiple payment accounts based on conditions.
¶ Service Payment Code Configuration
¶ Fixed Code
Single payment code for all transactions.
¶ Dynamic Code
Different payment codes based on conditions.
¶ 5. Payment Merchant Configuration
This is the merchant ID in IremboPay system
- Always fixed configuration
- Single merchant per service
- Format: Unique identifier provided by iremboPay (In our example: RRA-4ed26a32b0)
- This is the merchant ID in iremboPay system