Checking access…

Skip to main content
Version: v1

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.

info

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​

New Workflow​

API: High-Level Flow Diagram​

API: Applicable Scenarios​

apiScopeclientTypeuserTypeoutcome
usernew clientauthUser, agentallowed
userlegacy clientagentallowed
userlegacy clientauthUserrestricted
merchant-pci, merchant, merchant-wallet-managementany clientauthUser, agentrestricted

UI: High-Level Flow Diagram​

UI: Applicable Scenarios​

UI typesessionTypeuiModeuserTypechanneloutcome
new UIprimaryPAYMENT_WITH_WALLET, PAYMENT_METHOD_ENTRY, WALLET, PAYMENT_METHOD_SELECTauthUserwebformallowed
new UIprimaryPAYMENT_WITH_WALLET, PAYMENT_METHOD_ENTRY, WALLET, PAYMENT_METHOD_SELECTagentwebform, phone entryallowed
new UIchildPAYMENT_METHOD_ENTRYauthUserwebformallowed
legacy UIprimaryPAYMENT_WITH_WALLET, PAYMENT_METHOD_ENTRY, WALLET, PAYMENT_METHOD_SELECTagentwebform, phone entryallowed
legacy UIprimaryPAYMENT_WITH_WALLET, PAYMENT_METHOD_ENTRY, WALLET, PAYMENT_METHOD_SELECTuseranyrestricted
legacy UIprimary, childanyauthUseranyNA

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 CardNew CardCan update 'MF flag'?Can update 'default payment method' flag?Can update 'medication'?Can update other fields? (refer to list below)Outcome
Manufacturer CardManufacturer CardNoNoNoYesShow duplicate card message
Manufacturer CardRegular CardNoNoNoYesShow duplicate card message
Regular CardManufacturer CardNoNoNoYesShow duplicate card message

Other fields include: NickName, ZipCode, NameOnCard, ExpiryMonth, ExpiryYear, ZipCode