About Payment Methods Configuration
Configure the payments methods of your choice at Curlec Checkout.
You can configure the payment methods of your choice on the Curlec Checkout to provide a highly personalised experience for your customers. This provides a simple and accessible experience to your customers increasing your sales and your success rates.
Depending on the use cases that you might have, Curlec allows you to create any configuration of the payment methods, of your choice:
-
Highlighting certain payment instruments on the Checkout.
For example, Grab Pay could be displayed outside the Wallet block as a separate payment method. Maybank could come out of the FPX/Online Banking container as a different payment method. -
Restricting the kind of network, issuer, BIN and card type, different card properties, to accept payments.
For example, you can choose to accept payments only from "Maybank Visa Debit cards" on the Checkout. -
Removing a certain payment method or instrument.
For example, TouchnGo can be removed as a payment method from wallets. The entire FPX/Online Banking block or a certain bank in FPX/Online Banking can be removed from the Checkout. -
Reordering of payment methods on the Checkout.
You can choose to arrange Wallets as the first section instead of Cards on the Checkout. You can again order the PSPs within the Wallet block according to your need. -
Grouping of payment instruments.
For example, you can choose to group FPX/Online banking and Cards payment methods of a bank as a block that will be labelled as Pay via Bank on the Checkout.
To control payment methods on the Checkout, there are different ways to pass the configuration to the Checkout:
-
Configure via Dashboard: Choose the payment methods and instruments you want to display at checkout, arrange them in your preferred order, and tailor the checkout experience to match your business needs. Create custom payment blocks for specific customer segments on the Razorpay Dashboard. Know more about
. -
Pass Configuration at Runtime: Pass the configuration to the
for details.options
parameter of the Checkout code at the run time. This is useful when you want to modify the order of the payment methods for a particular set of payments while rendering the Checkout. See the -
Use a Configuration ID: Create a global setting of the payments as a Configuration ID and pass these values while creating the Order. This is useful when you want control the checkout configurations dynamically using different Configuration IDs. You can create a Configuration ID through the
.
Is this integration guide useful?