To begin setting up recurring credit card agreements, you must first verify that your payment service provider is properly configured to allow the collection of credit card transactions. Depending on your payment service provider, we also support zero-amount payments. This allows for the initial agreement to be signed without immediately charging the customer.
To create a credit card Profile, navigate to Settings > Profiles and click on + New:
Once created, the Profile and the selected Gateway are now configured for both One-Off and Recurring payments.
The necessary Attributes are automatically configured on the Profile. While you can add new attributes to the profile, it is strongly advised not to remove any of the preset attributes. Some are essential for processes like signing the agreement, collecting payments, or sending notifications about card expiry.
When inviting a customer to sign a credit card agreement, you have two options:
When a new credit card agreement is created, an associated payment link is also generated. Once the document is signed, we update the Attributes on the agreement based on the information received from your payment service provider. This information exchange is one-to-one between Twikey and your PSP.
Recurring credit card transactions (RCC) are processed differently from Direct Debits. When a credit card transaction is created, it is directly placed into a transaction batch. Unlike traditional transactions, you do not need to send this batch to the bank, except when RCC transactions are reoffered. After a short period, the transaction(s) are sent to the payment provider, and you subsequently receive feedback.
A new batch for recurring credit card transactions is automatically generated each day upon the creation of the first RCC transaction of the day. This batch contains all that day's transactions. Feedback for these transactions is provided on an individual basis.
When we receive a failure on a transaction from your provider, we attempt to map it as closely as possible to standard R-codes. This allows for the correct dunning steps to be automatically taken. Because each payment service provider has its own unique feedback mechanism, we may occasionally be unable to map the failure. In such cases, we use the general error code PY01 (Technical failure).
A single webhook of type=payment is sent out on the day after receiving payment information for a batch (covering one or more transactions), provided your Gateway is one of the following: