Created with Sketch.
Created with Sketch.

Checkout 3.0

Simplicity for merchant

Avarda Checkout offers several different payment methods with one integration and one agreement. Responsive streamlined white labelled user dialogues which can be customized on-demand ensure a high conversion rate both for desktop and mobiles devices.

Simplicity for consumer

Fewer steps are required to complete your online purchase, address lookup and “remember me”-functionality gives recurring customers a “one-click buy”-experience. The different delivery address is supported for all payment methods and the application prevents ID thefts.

Features

  • Invoice payments
  • Account/loan pay in your own pace
  • Part payments (3, 4, 6, 12, 24, 36, 48, 72 month)
  • Visa/Mastercard payments
  • Direct bank payments for Finland
  • Swish for Sweden
  • Vipps for Norway
  • ElectronicID validation
  • B2B invoice support
  • Brandable for merchant, logos, colors, fonts And much more…

What needs to be prepared?

  • Sign Agreement with Avarda. Contact sales@avarda.com if you want to know more or get help.
  • Avarda creates user credentials for API:s and configure payment methods and options.
  • Merchant installs E-com module or integrates towards Avarda checkout.
  • Test, Launch and Go live.

Avarda checkout process overview 

Initialization

The Initialization process is triggered when the user navigates to the checkout page on the merchant site. Merchant initializes checkout session by calling Avarda API, using appropriate credentials

Obtain Payment info

Merchants website loads a checkout form for the session initialized in the previous step. The user fills in purchase details and optionally modifies the contents of the shopping cart. The checkout form continuously updates the checkout session by communicating with Avarda API as the user proceeds to fill in purchase details.

Finalize purchase

When the user hits the “complete payment ” button a request is sent to Avarda API. Merchant is notified by Avarda API about the successful completion of the payment and the user can be redirected to a confirmation page.

Avarda technical checkout process overview

Initialize

Get access token to checkout APIs using your ClientID and Secret provided by Avarda. The access token can/should be reused for all your checkout requests until it expires after one hour. Access token reuse is for performance reasons and will decrease the load time of the checkout.

Initialize the checkout session by calling API Purchase – PurchaseID and JWT token is returned. Use AccessToken as bearer in your header request to authenticate.

Update (optional)

Load the checkout form via Avarda Javascript using the JWT token from API Purchase. Details described in how to embed checkout form. During the time when the checkout form is active, it can be updated with changes from the shopping cart (updateItems) or eventual delivery address updates from a parent page. Parent page can also receive events for validating delivery address or order status before purchase is completed.

Finalize Purchase

Complete payment. When the user completes the payment, checkout form triggers the java script event CompletePurchaseCallback which notifies the parent page to check status and if status is completed load the confirmation page.

Payment status should be checked after the purchase is completed. Merchant calls checkout API purchases with the purchaseid as a key and receives a full data object back with all information that has been generated during the checkout.

Order Management

Delivery

GetAccessToken using your ClientId and Secret. Reuse token for 1h and send it as Bearer in http header for api authentication.

PurchaseOrder. On delivery Avarda expects a message with all delivered products – This message is the base for when merchant gets paid for orders and when the end customer is invoiced. Part delivery is allowed. Discounts can be sent in same call using negative amount.

Return

GetAccessToken using your ClientId and Secret. Reuse token for 1h and send it as Bearer in http header for api authentication.

ReturnOrder. If merchant gets some goods in return or need to credit the end customer this message is expected. End customer will be credited on their invoice or amount refunded for prepaid card or direct bank payments.

Cancel

GetAccessToken using your ClientId and Secret. Reuse token for 1h and send it as Bearer in http header for api authentication.

Cancel. If order cant be delivered and needs to be cancelled. Refund of the total authorized amount will be performed to end customer if prepaid, credit reservation on invoice will be removed.

Refund

GetAccessToken using your ClientId and Secret. Reuse token for 1h and send it as Bearer in http header for api authentication.

Refund. If prepaid order is not fully delivered, refund to end customer is required. Refund specific amount.

Refund Remaining. Refunds all not yet debited (purchaseOrder) amount to end customer.

DEMO Shop

Example

Contact

SWEDEN 
info@avarda.se

FINLAND 
info@avarda.fi