Experience Integration
Client Experience
This section outlines the UX and functionality based on different possible values for the experienceId parameter in the v2/sessions API. Each section will cover potential use cases and functionality differences across our experience offering. If not left blank, there are three possible values, described below:
Default Direct Integration - Managed Payment Experience
This experience is intended to minimize the dev work required to integrate payment functionality. Merchants that will need to process payments while the customer is in session and do not need to host wallet functionality should consider this experience.
In the experience, the customer authorizes payment through the Link Money client. Link Money handles the v1/payments API call and returns a payment response along with customer information.
Once integrated there's no need for additional integration with the standalone v1/payments API. To enable this experience, set the experienceId field to LINK_MANAGED_PAYMENT and provide the required payment details.
PSP - Payments Experience Integration
Here, the customer authorizes payment through the Link Money client, and Link Money returns customer information that maps to linked accounts and enables payments. PSP’s are expected to create a mapping to the v1/payments API from their merchant facing endpoints. Merchants can use the customerID captured from the query parameters and schedule payments.
This experience is ideal for PSP’s or when aligning with existing integrations. To enable this experience, work with the Link Money team to assign this experience type as the default at the merchant level. If you have multiple experience requirements across your UX, such as a wallet functionality or customer out-of-session payments, set the experienceId field to ONBOARD_WITH_PAY_NOW at the appropriate v2/sessions call instances.
Direct Integration - “Adding a payment method”
In this experience, the customer links an account via the Link Money client and authorizes the connected account for future debits. Link Money returns customer information that maps to linked accounts in the query parameters. Merchants should save CUSTOMER_ID and use the v1/customers/accounts API to access linked account details during future transactions.
This experience is recommended for scenarios such as wallet funding and subscription-based use cases. To enable this experience, work with the Link Money team to assign this as the default value. If you have multiple experience requirements across your UX, set the experienceId field to ONBOARD_WITH_DONE at the appropriate v2/sessions call instances.
Account Management & Returning Customer Experience
Link Money provides a secure and expedited experience for returning customers, enabled through device possession confirmation and internal risk modeling. Once customers link and authorize their account, they can opt to "Enable Future Faster Payments" by submitting a One-Time Passcode (OTP) sent via SMS or email. This results in a significantly faster returning customer experience, while still providing a high level of risk and fraud prevention.
