Overview
Merchants may integrate with PazeSM directly or indirectly depending on their existing tech stack and how they work with their service providers. Paze supports Merchants that have in-house commerce and payment processing capabilities, as well as Merchants that work with service providers for one or both of those functions.
In general, a Merchant’s Paze integration should follow the pattern below (error states have been omitted for clarity).
Integration Process
| Action | Response |
|---|---|
| Consumer enters cart or account management page | Commerce site invokes initialize API to start running fraud checks |
| Consumer initiates Paze | Commerce site invokes checkout API to launch Paze user interface (UI) |
| Consumer selects payment and shipping information and exits Paze UI | Commerce site displays consumer details sent by Paze |
| Consumer chooses to change selected payment card or shipping information | Commerce site invokes checkout API to relaunch Paze UI |
| Consumer selects payment or shipping information and exits Paze UI | Commerce site displays updated consumer details sent by Paze |
| Consumer finalizes purchase | Commerce site invokes complete API to initiate transaction |
| Paze generates encrypted payload for transaction | Commerce site provides payment processor with encrypted payload’s identifier |
| Payment processor invokes getPayload API | Paze sends encrypted payload to payment processor |
| Payment processor decrypts encrypted payload and submits it for processing | Commerce site displays transaction success message to consumer |
Updated about 1 month ago