This functionality is available for the following models:
Credit cards have global coverage and are one of the most popular ways to pay online. There are different types of cards and several steps in the process. Learn how it works, the parties involved, and the stages of a subscription payment.
A credit card payment for a subscription is made in 2 main steps: Credit or debit card registration and execution of the recurring charge.
In your website or app, the user will select the payment method. Make sure that it is clear for the payer that their credit or debit card will be registered for paying a recurring value.
At this step, the user provides the data of the card that he/she will use to pay. Your website or app should be capable of verifying that the card information is correct (for example, that the expiration date is not outdated, or that the card number can be validated using Luhn’s algorithm). In this step, it cannot be yet warranted that the card is valid.
Kushki will receive these data and will verify whether there are enough funds in the account associated to the credit or debit card by using a charge for subscription validation. This small fee is charged by Kushki and is automatically reversed if successful. This fee ensures that your client’s credit card can be charged after registration.
At this step, we will inform you about the result of the card registration process, so that you can show it on screen to the user.
Kushki processes recurring charges to the registered card automatically. Payments will be executed and repeated according to the amount and period indicated in the subscription.
The billing logic starts running every day from 6am GMT-5. Make sure that the subscription was created before this time if you want the first payment to be executed on the same day of registration. Alternatively, your customer can register his/her card some days in advance, before Kushki executes the first charge. When creating a subscription, you must indicate the start date
If a payment is rejected, Kushki has a retry logic to try to recover the charge. By default, there are 3 retries for 3 days in a row from the payment day originally defined in
startDate. For example, for a monthly subscription with start date:
10-01-2021, with a rejection on
10-02-2021, payment will be retried until
13-02-2021, 3 times each day, for a total of 9 payment attempts.
You can modify the retry days for a subscription and also define specific charging days.
If the last charge attempt was declined, we may send you a notification via WebHook informing you about it. In these cases, we recommend you to contact the card owner and offer him/her a set of alternatives for paying the fee that could not be charged; for example, changing the registered credit card and generating a charge on demand only for one time. Kushki will continue executing automatic charges over the following periods.
You can choose the frequency of recurring charges by submitting any of these values in the required
- daily: every 1 day.
- weekly: every 7 days.
- biweekly: every 15 days.
- monthly: every 30 days.
- threefortnights: every six weeks or 42 days.
- bimonthly: every 60 days.
- quarterly: every 90 days.
- fourmonths: every 120 days.
- halfyearly: every 180 days
- yearly: every 360 days.
- custom: for one click payments.
At this step, you will be notified of the status of each automatic charge. You may receive the Webhook notifications that you expose for Kushki to consume. You also use Kushki’s console to verify transactions, as well as their details and their status.
Start your integration and accept recurring payments online safely.
Register a Card
Start your integration and accept recurring online payments.
Handle post-payment events in the right way.