Paze recognizes a consumer wallet by an email address or mobile phone number. However, the way in which a consumer’s email address or mobile phone number are collected is configurable based on a Merchant’s preference. In keeping with the Paze core principle of offering flexible implementation options, Merchants may choose to present the Paze experience differently depending on the consumer’s journey through the Merchant’s digital property.

Note: Merchants should confirm that they have provided all disclosures, notices, and options to consumers required under applicable law and privacy requirements in order to provide or otherwise make available information or data to Paze℠ for use in the service. Before the consumer is redirected to the Paze℠ experience, Paze℠ may collect several data attributes when the Initialize API is called, such as email address, device ID, IP address, and browser. Such information is collected by Paze℠ and may be disclosed to third-party vendors to make fraud risk decisions throughout the checkout experience.

When deciding on initiation points, Merchants will need to assess the tradeoff between consumer convenience and wallet accessibility. Providing an email address or mobile phone number on a consumer’s behalf preempts manual data entry; however, it runs the risk of not matching the consumer to their wallet. This will occur if the consumer has different email addresses or mobile phone number for their issuer(s) and the Merchant.

Static Button Initiation

A Merchant may want to integrate with Paze by placing a static button on their website. This gives consumers the option to click into the Paze experience at their discretion.

Note: The static button can be implemented for registered users with or without reference to their email address or mobile phone number on file with the Merchant.

Figure 5 Status Button Initiation Example — Figure 6 Status Button Initiation Example

Status Button Initiation Consumer Outcomes

User Status	Wallet Status	Outcome
Guest	Exists	User clicks button, Paze launched, user enters email or phone number in Paze
Guest	Does not exist	User clicks button, Paze launched, user enters email or phone number in Paze, user gets error and returns to Merchant site
Registered	Exists	User clicks button, Paze launched, user enters email or phone number in Paze
Registered	Does not exist	User clicks button, Paze launched, user enters email or phone number in Paze, user gets error and returns to Merchant site

Dynamic Button Initiation

A Merchant may want to allow consumers to choose from multiple payment methods, while also preventing them from seeing options that they cannot use. By adding logic that only shows a button to consumers who have an active wallet with Paze, Merchants can prevent consumers from entering a flow that they cannot complete.

Dynamic Button Initiation Example

User Status	Wallet Status	Outcome
Guest	Exists	User enters email or phone number on Merchant site, Merchant checks for Paze, user shown button, Paze launched
Guest	Does not exist	Merchant checks for Paze, user shown button, Paze launched
Registered	Exists	Merchant checks for Paze, user not shown button
Registered	Does not exist	Merchant checks for Paze, user is not shown the button

Automatic Initiation

A Merchant may want to offer Paze to eligible consumers. By sending consumers’ email addresses or mobile phone number to Paze without adding a button to their site, Merchants can direct eligible consumers to the Paze wallet without impacting ineligible consumers’ experience on their site.

Note: With automatic initiation, for consumers who accidentally exit Paze to allow them to re-enter, it’s strongly suggested to include a static Paze button on the primary checkout page. If a consumer exits Paze, they should be taken to the Merchant primary checkout page and not placed back into the Paze flow.

Merchants are recommended to perform frontend validation to confirm that data has been entered into the email address or mobile phone number fields before calling the Paze Checkout API. Otherwise, defocusing from that field when it is empty will launch an experience that requires the consumer’s email address or mobile phone number to be collected within Paze.

Automatic Initiation Example

User Status	Wallet Status	Outcome
Guest	Exists	User enters email or phone number on Merchant site, Merchant gives email to Paze, Paze launched
Guest	Does not exist	User enters email or phone number on Merchant site, Merchant gives email to Paze, Paze not launched
Registered	Exists	Merchant gives email or phone number to Paze, Paze launched
Registered	Does not exist	Merchant gives email or phone number to Paze, Paze not launched