Add Manufacturer Card
The new Manufacturer Card flow enhances functionality by requiring MF cards to be associated with a medication, ensuring a structured and meaningful linkage to their intended use.
The "Add Manufacturer Card" feature ensures compatibility across legacy and new clients, enabling seamless management of manufacturer cards while supporting updated business rules without disrupting existing workflows.
This documentation outlines the workflows, API use cases, and UI use cases for both legacy and new clients, ensuring a smooth transition and backward compatibility.
From merchant perspective, Manufacturer card addition is only supported in UI widget integration, not via API.
MF card category configuration is bypassed for legacy clients, allowing MF cards to be added without restrictions.
Legacy MF, Legacy Client, New Clientβ
- Refer Terminology
New Workflowβ
API: High-Level Flow Diagramβ
API: Applicable Scenariosβ
| apiScope | clientType | userType | outcome |
|---|---|---|---|
| user | new client | authUser, agent | allowed |
| user | legacy client | agent | allowed |
| user | legacy client | authUser | restricted |
| merchant-pci, merchant, merchant-wallet-management | any client | authUser, agent | restricted |
UI: High-Level Flow Diagramβ
UI: Applicable Scenariosβ
| UI type | sessionType | uiMode | userType | channel | outcome |
|---|---|---|---|---|---|
| new UI | primary | PAYMENT_WITH_WALLET, PAYMENT_METHOD_ENTRY, WALLET, PAYMENT_METHOD_SELECT | authUser | webform | allowed |
| new UI | primary | PAYMENT_WITH_WALLET, PAYMENT_METHOD_ENTRY, WALLET, PAYMENT_METHOD_SELECT | agent | webform, phone entry | allowed |
| new UI | child | PAYMENT_METHOD_ENTRY | authUser | webform | allowed |
| legacy UI | primary | PAYMENT_WITH_WALLET, PAYMENT_METHOD_ENTRY, WALLET, PAYMENT_METHOD_SELECT | agent | webform, phone entry | allowed |
| legacy UI | primary | PAYMENT_WITH_WALLET, PAYMENT_METHOD_ENTRY, WALLET, PAYMENT_METHOD_SELECT | user | any | restricted |
| legacy UI | primary, child | any | authUser | any | NA |
Dedupe logicβ
When a new card is added to the wallet, the system checks for duplicates. If the card is identified as a duplicate, the following rules determine which fields are copied from the new card to the existing card. The dedupe logic remains consistent for both legacy and new clients.
| Existing Card | New Card | Can update 'MF flag'? | Can update 'default payment method' flag? | Can update 'medication'? | Can update other fields? (refer to list below) | Outcome |
|---|---|---|---|---|---|---|
| Manufacturer Card | Manufacturer Card | No | No | No | Yes | Show duplicate card message |
| Manufacturer Card | Regular Card | No | No | No | Yes | Show duplicate card message |
| Regular Card | Manufacturer Card | No | No | No | Yes | Show duplicate card message |
Other fields include: NickName, ZipCode, NameOnCard, ExpiryMonth, ExpiryYear, ZipCode