Optimize your buyer experience, Fastlane member experience, integration, and styling.
Make sure your buyers have the ideal Fastlane experience by following these best practices.
You must show the PayPal button upstream in the cart page or alongside the Fastlane email field to ensure consumers have the option to use their PayPal account.
Because Fastlane accounts are looked up by email address, the email address field needs to be the first step of the checkout process. If a profile is found, Fastlane retrieves shipping and payment information for the Fastlane member. If the email comes later in the process, it makes a confusing experience.
Render the Fastlane watermark below any merchant-rendered fields for full consumer transparency. The watermark contains a link where a buyer can go to see the Fastlane terms of service.
After a registered Fastlane member has been authenticated and the profile information is received, hide any of the member's other payment methods under a single link.
When a buyer enters the OTP, their intent is to use Fastlane. Any additional areas of the UI, such as other payment methods, should be available to give the buyer as many choices as possible. However, keeping the page simple and minimalistic helps the user focus on the transaction.
After a Fastlane member authenticates, there are a few best practices that you should implement to further reduce friction during the process:
- Put the user at the order review page, or your site's equivalent.
- Ensure the least expensive shipping option is automatically selected.
- Render a change button for the shipping address. That change button should call the
showAddressSelector()
method of the client SDK. This invokes the shipping address selector allowing the buyer to select from shipping addresses or add a new one. - Render a change button for the card being used for the purchase. That change button should call the
showCardSelector()
method of the client SDK. This invokes the card selector, allowing the buyer to select from other cards or add a new one to their profile. - For other use cases, such as adding a gift message, you can direct a return user to land on that specific page.
Optimize your integration by following these best practices.
Always make sure to load the Fastlane on the onload
event of your checkout page. Attempting to load the SDK after a user interacts with the page may cause conversion issues.
While this is always a best practice, it is particularly important in regards to Fastlane. In cases where the buyer adds a shipping address or a new card to their profile, the changes only apply once the token and address info is sent via /v2/checkout/orders
.
Call the triggerAuthenticationFlow()
method every time the checkout page is reloaded. There is internal logic within our SDK that determines whether we require the buyer to authenticate via OTP again or restore the session. In either case, the method returns the authenticatedCustomerResult
. This also includes a new single-use token.
Whether you're using our components or rendering a Fastlane profile information yourself, a change button is required.
You can render the ability to edit information in the way that best fits the look and feel of your site checkout. Have the onclick
event call the profile.showShippingAddressSelector()
or profile.showCardSelector()
to launch the necessary modals.