Managing Recurring Payments
Recurring Billing tools provided in Parallels Business Automation - Standard allow you to charge your customers on a recurring basis, automatically. Recurring billing makes it possible to set up regularly scheduled payments, such as subscription fees.
The order of payment methods usage for recurring payments in Parallels Business Automation - Standard is the following:
- Check the payment amount in respect to the maximal amount to be paid recurrently.(Commerce Director - Payment Processing - General Configuration).
- Check the payment amount in respect to the minimal amount to be paid online. (Commerce Director - Payment Processing - General Configuration).
- Check for credit cards allowed for recurring payments and in OK status.
- If no applicable credit cards found, check for the applicable bank accounts (allowed for recurring payments and in OK status).
For recurring billing to work, customers credit card or bank account data must be stored in Parallels Business Automation - Standard database, so billed amount can be automatically withdrawn from a customer credit card or bank account without the need for you to enter a payment method requisites.
Thus, the first thing to do to set up the recurring billing, is making it possible to store credit cards and bank accounts in Parallels Business Automation - Standard, i.e., secure storage configuration.
Then, you need to make sure that payment methods data will be saved in Parallels Business Automation - Standard:
- Special setup is needed. Credit cards are not necessarily must be stored in Parallels Business Automation - Standard to make payments (some payment plug-ins redirect payers to payment gateway web payment pages and a payment can be submitted directly, beside Parallels Business Automation - Standard). But to use recurring billing with credit cards, you must set credit cards processing to save credit cards data in Parallels Business Automation - Standard database (Commerce Director - Payment Processing - Secure Storage - General Settings).
- No need for additional settings. Bank accounts data is being always saved as soon as the secure storage is configured, since one-step payments by bank accounts are not possible. Bank accounts requisites are to be included in transaction requests (batch files) that can be generated only manually, and it takes some time to compose a batch, so if a bank account requisites were not saved - a transaction request cannot be submitted to a bank.
Finally, to make recurring billing more secure, you can impose some restrictions for payments being processed recurrently: amounts to be processed, number of attempts to pay a document recurrently, etc. (Commerce Director - Payment Processing - General Configuration).
Please send us your feedback on this help page