Fastlane SDK Wrapper #2985
Merged
Fastlane SDK Wrapper #2985
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ribeiroguilherme
requested review from
marcperez,
pabloai,
sponglord,
m1aw and
longyulongyu
as code owners
|
ribeiroguilherme
force-pushed
the
fastlane-sdk-wrapper
branch
from
7cfd5d0 to
0b5a750
Compare
|
Size Change: +4.43 kB (+0.58%) Total Size: 772 kB
ℹ️ View Unchanged
|
size-limit report 📦
|
|
longyulongyu
approved these changes
Dec 2, 2024
ribeiroguilherme
added a commit
that referenced
this pull request
Dec 3, 2024
* draft stories * cleaned up stories and code * cleaned up types * fixed types * removed comment * fastlane wrapper unit tests * returning component config * random commit
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
initializeFastlane)request-fastlane-token.tscurrently does not work and is being fixed by LPMHow it works:
Merchant initializes Fastlane by doing:
Then, once the shopper email is collected by the merchant, the merchant triggers the authentication flow by doing:
The
authResultmay contain the shopper profile with his Card or just the flag saying profile was not found. Based on that, the merchant can request the Adyen Component configuration:The configuration will contain the config related to Fastlane component or Card component based on the
authResult. (For Card we need the consent details data, whereas for Fastlane we need the last four digits, brand, etc)..Bonus: The merchant can also mount the Fastlane watermark by doing: