Smart Checkout Functionality & Options
An overview of the key functionality & options offered by Smart Checkout.
- Styling & design
- Checkout language
- Save payment cards for future use
- Decline recovery
- Field validation
- Form auto-complete
- Automatic card logo display
- 3DS challenge flow
- Payment order expiry
- Pay by card installments
- Recurring payments
- Get Support
Styling & design
Add your brand logo
We would highly recommend you show your company logo on your Smart Checkout payment pages in order to increase customer recognition and trust, thus improving conversion. You can insert your company logo while creating a payment source for Smart Checkout.
You can also change or update this logo at any time, for any given payment source. To do this, please see our adding your brand logo tutorial for a step-by-step guide.
Add your brand color
You can also add your preferred brand color to your Smart Checkout payment pages in the form of a URL parameter. Please see the specify brand color section of our Smart Checkout Integration guide for further information.
Display a cancel button on Smart Checkout
When you activate the cancel button on Smart Checkout, your customers will have the ability to cancel their orders directly from the Smart Checkout. Please see the display a cancel button on Smart Checkout section for further information.
The language that Smart Checkout is presented in is determined according to this sequence:
- Language specified as a query parameter during the redirect by the merchant
- Language selected by the customer during a previous checkout
- Language specified during the creation of the payment order by the merchant
- Dominant language in the customer country
Save payment cards for future use
Smart Checkout offers customer-side card tokenization. This means that the customer can save their card and reuse it while on Smart Checkout across merchants and countries. Customers can save cards once, and use everywhere.
The merchant is not involved in this process; in fact, you will not even be aware that your customers are using a saved card. In technical terms, this means that you will not receive any card tokens yourself; the card token will remain on the browser of the customer.
- Saving a card: the customer will be offered the option to save a card and assign a friendly name
- Paying with a saved card: the customer can select a saved card to pay; they will be required to provide the CVV to use it (to ensure SCA)
- Editing or deleting a saved card: the customer can delete a saved card, or change the friendly name assigned to the saved card
Saving a card
The customer is able to save their card details during payment, as shown below:
Paying with a saved card
When paying, the customer is able to select which of their saved cards to use:
Editing or deleting a saved card
If desired, the customer can click on the edit (pencil) icon to edit or delete a saved card:
From here, the customer can either:
(1)rename the saved card before clicking the tick button to save it
(2)delete the saved card
When attempting to delete a saved card, a prompt will be shown, asking the customer to either cancel or complete the deletion:
When a payment is declined, if certain criteria are satisfied, then we prompt the customer to try again with either the same payment method or with a different payment method.
The criteria examined to trigger the decline recovery will be constantly fine-tuned going forward to ensure ever-improving results.
By performing decline recovery, the conversion rate improves, with a significant portion of recovered declines resulting in a successful payment.
This feature is automatically enabled for all merchants, and thus merchants do not need to do anything, on their online store or to their integration with us, to take advantage of this new conversion-improving feature.
There are two categories of validation available on Smart Checkout, Inline and On Submit, as described below:
This type of validation occurs instantly as the customer moves between fields, but only if text has been entered.
- Email address — has to be a valid email address
- Card number — has to be a valid card number
- Expiration date — past dates are not allowed
- CVV — is required for all cards except for Bancontact cards. If the customer has provided an AMEX card, the CVV has to be four digits long, otherwise it has to be three digits long
- Amount (if editable by the customer, i.e. for Quick Pay) — has to be a valid amount, greater than zero
- Cardholder name — has to be more than one character long, and can only contain latin letters and spaces (as shown below)
On Submit validation
This type of validation occurs once the customer has clicked on the button to make the payment.
- All mandatory fields must be filled (cannot remain blank)
Smart Checkout allows the customer to auto-complete their card details if this functionality is supported by their browser. In such cases, the customer can select the desired payment card from a dropdown and the form will be completed with the respective card details.
Automatic card logo display
The card logo is displayed once the customer has started entering the card number. For most cards, only two digits are necessary before the card is identified and the card logo is shown. Maestro and Bancontact are exceptions, with three and four digits required respectively before this will occur.
3DS challenge flow
The card issuer may choose to initiate a 3DS (3D Secure) challenge. In such a case, the issuer requires additional customer interaction, either through biometrics, two-factor authentication, or similar methods.
Payment order expiry
If the customer is unable to make a payment because the checkout process has expired, then the customer should go back the merchant store and restart the checkout process. The
paymentTimeout parameter can be used to set the expiry time when creating a payment order
Pre-authorization (pre-auth) transactions with a debit card or credit card hold the balance as unavailable either until the merchant ‘captures’ the transaction or the hold ‘falls off’. The latter is automatically done after a certain period, at which point the pre-authorization is ‘lost’ and can no longer be captured.
A pre-authorization is enabled if the following condition is met:
isPreAuthrequest body parameter within the create payment order API call is set to
More information on handling pre-authorizations (including creating, capturing and cancelling) can be found on our tutorial page.
Pay by card installments
The option to pay by card installments is enabled if the following three conditions are met:
maxInstallmentsrequest body parameter within the Create payment order API call is set to greater than
1and up to
- The merchant account is Greek and set up in Greece. Accounts originating in other countries do not support this
- The customer’s card supports installments
Please note: If offering installments, the value provided by the merchant is not the number of installments the customer will select, and it is not mandatory for the customer to select installments at all. The process is as follows:
- The merchant indicates the maximum number of installments they wish to offer to the customer
- It is then up to the customer whether they pay with or without installments
- If the customer decides to pay with installments, they are able to select the number of installments (up to the maximum specified by the merchant)
The merchant also has the option to force a specific number of installments on a payment order by using the
forceMaxInstallments parameter and setting it to
true. When used, please note that the following conditions apply:
- It is mandatory for the customer to pay with installments and with the specific number indicated
- Only cards supporting installments can be used for the payment
- The value set within the
maxInstallmentsparameter dictates the number of installments that will be forced to the customer. It should be >
0, otherwise the call will return an error
More information on payment by card installments can be found on our tutorial page.
A recurring payment A.K.A. a subscription is initiated by the merchant without the involvement or presence of the customer (no 3DS authentication is required), done on a regular or non-regular schedule, for a fixed or variable amount. This requires an initial payment to be made with the involvement of the customer, during which the customer provides consent to the merchant to make future automatic payments (recurring payments). Recurring payments can be created via API and from within the Viva account (self-care).
More information on recurring payments/subscriptions can be found on our tutorial page and payment tools page.
If you would like to integrate with Viva, or if you have any queries about our products and solutions, please see our Contact & Support page to see how we can help!