Returning Shoppers Guide

Optimize the checkout experience for returning shoppers, with BlueSnap's Payment API

It is easy to make a VIP checkout experience for returning shoppers and improve your conversion rates by pre-populating your checkout page with the shopper's saved information. Then the shopper can complete checkout in a single click!

Follow these steps to build a great checkout experience for your returning shoppers:

Step 1: Create a vaulted shopper

If you’ve asked the shopper to create an account or log in to your site, then one-click checkout becomes really easy to achieve using BlueSnap’s Payment API. All you have to do is "vault" your shopper. This means you send BlueSnap the shopper name and payment info, then we’ll save the shopper information for future use and send you an ID for that shopper's record in our system. Since this information is stored by BlueSnap, you get the benefit of ultra-streamlined checkout for returning shoppers, with no need to worry about encryption and security headaches.

BlueSnap will automatically return a BlueSnap token ('vaulted-shopper-id') to you in response to a card transaction request like an Auth Capture.

Alternatively, you can save the shopper info before processing a transaction, by sending BlueSnap a Create Vaulted Shopper request. Below is an example of a Create Vaulted Shopper request for a shopper with a credit card.

<vaulted-shopper xmlns="http://ws.plimus.com">
   <first-name>Jane</first-name>
   <last-name>Smith</last-name>
   <payment-sources>
      <credit-card-info>
         <credit-card>
            <card-number>4000111122223333</card-number>
            <security-code>111</security-code>
            <card-type>VISA</card-type>
            <expiration-month>07</expiration-month>
            <expiration-year>2023</expiration-year>
         </credit-card>
      </credit-card-info>
   </payment-sources>
</vaulted-shopper>

BlueSnap sends a response to the Create Vaulted Shopper Request, with the ID number we assigned to that stored shopper. For example, Jane Smith's BlueSnap token in the response below is 12345678.

HTTP/ 1.1 201 Created
Location: https://sandbox.bluesnap.com/services/2/vaulted-shoppers/12345678

Step 2: Retrieve the shopper details and prepopulate the checkout page

Once you have stored a shopper and obtained the BlueSnap token, the optimized checkout experience becomes very easy.

Whenever your saved shopper (in this example, Jane Smith) logs in to her account, you can easily retrieve her payment details by sending a Retrieve Vaulted Shopper request, with Jane Smith's shopper ID included in the API call. Here is an example (in cURL), with the shopper ID highlighted in blue:

490

BlueSnap will then reply with Jane’s saved information, including her card details, so you can populate the information in the checkout form.

405

Now checkout is streamlined and as easy as possible. All Jane has to do is click “Buy Now” to make the purchase!

👍

Capturing CVV during checkout

We recommend capturing the shopper’s CVV during checkout and including this value within the transaction request to BlueSnap. Transactions with CVV generally result in higher success rates since the issuers' fraud and risk engines consider these transactions to be a lower risk.

For code examples, see Auth Capture or Auth Only.

Step 3: Complete the purchase using the vaulted shopper ID

When Jane clicks buy now, you can easily complete the purchase based on her BlueSnap token. Simply send in the relevant transaction request, such as an Auth Capture, and include the "vaulted-shopper-id'. If there are multiple credit cards saved to that vaulted shopper, make sure you include the relevant card's last four digits, and the card type.

<card-transaction xmlns="http://ws.plimus.com">
   <card-transaction-type>AUTH_ONLY</card-transaction-type>
   <amount>75.00</amount>
   <currency>USD</currency>
   <vaulted-shopper-id>12345678</vaulted-shopper-id>
   <credit-card>
      <card-last-four-digits>3333</card-last-four-digits>
      <card-type>VISA</card-type>
   </credit-card>
</card-transaction>

This means there is no need to store the shopper details on your end, and the complete purchase flow is simple for both the shopper and the merchant!