Appendix
Fastlane profile data priority
The following table lists the required data to create a Fastlane profile, how you can pass the
information, and which takes priorityData Property
Data Property | 1st Priority | 2nd Priority |
---|---|---|
Phone Number | UI | N/A |
UI | N/A | |
Billing Address | API | UI - Tokenize |
Shipping Address | API | UI - Tokenize |
First Name | Derived from Billing Address First Name | N/A |
Last Name | Derived from Billing Address Last Name | N/A |
FAQs
Will Fastlane work if I save payer’s payment methods?
Yes, however, the paymentToken
returned on the client can be vaulted prior those
creating a transaction on your server. Be aware that we only support vaulting when using the
store_in_vault_on_success
boolean in the transaction.sale()
request.
Fastlane does not support a flow where a customer or payment_method
is created before a
transaction. We hope to support this in a future release.
How long is a paymentToken valid for?
A paymentToken
is valid for 3 hours from the time of issuance.
What if the payer’s shipping address is in a location my site does not ship to?
When you initially call braintree.fastlane.create()
you have the option of passing in a
list of allowed locations using the addressOptions
object. See the Reference Types
section for details.
How should I handle cases where a payer navigates away from the checkout page to add or remove
items?
It is best practice to call the triggerAuthenticationFlow()
method every time the
checkout page is reloaded. Internal logic within our SDK will determine whether we will require the
payer to authenticate via OTP again or simply restore the session. In either case, the method will
return the authenticatedCustomerResult
. This will also include a new
paymentToken
.