Digital Wallet Notifications
A great way to reduce fraud exposure is to notify your cardholders when someone has attempted to add their card to a Digital Wallet such as Apple Pay™. If you are integrated with Marqeta through Treasury Prime, the token-activation-request
card event allows you to know when a card was attempted to be added to a Digital Wallet so that you can notify the cardholder.
Crafting a User Notification
In the networkdata
of the token-activation-request
, there is a token_service_provider
sub-object that contains information about the token requestor that you can use to inform the notification that you send to the cardholder. Sending this notification allows the cardholder the opportunity to reach out immediately in the case of potential fraud.
token_service_provider sub-object
Parameter | Type | Description |
---|---|---|
token_type | string | Comma-delimited list of digital wallet token types. |
correlation_id | string | A unique value representing a tokenization request (Mastercard only). |
token_reference_id | string | Unique identifier of the digital wallet token within the card network. |
token_requestor_id | string | Unique numerical identifier of the digital wallet token requestor within the card network. These IDs map to a token_requestor_name . |
token_requestor_name | string | Name of the token requestor within the card network. |
Example token_service_provider sub-object
"token_service_provider": {
"token_type": "DEVICE_SECURE_ELEMENT",
"correlation_id": "D0008606521111",
"token_reference_id": "DAPLMC0000264791e37c56b00ce24194bda69345f4999000",
"token_requestor_id": "50110030273",
"token_requestor_name": "APPLE_PAY"
}
Token Requestors
You will see the following token_requestor_name
and token_requestor_id
in the token_service_provider
sub-object which you can use to determine what Digital Wallet Provider the card was added to when crafting your messaging.
Network | token_requestor_name | token_requestor_id |
---|---|---|
Mastercard | APPLE_PAY | 50110030273 |
Mastercard | ANDROID_PAY | 50120834693 |
VISA | APPLE_PAY | 40010030273 |
VISA | ANDROID_PAY | 40010075001 |
Example Communication
Below is an example communication that can be used as a starting point to build your own messaging.
Note: Please work with your partner bank to ensure communications are approved.
Dear [Cardholder Name],
Your [Issuer Name] debit card has been added to [Token Requestor Name] Pay™.
We're excited to offer [Token Requestor Name] Pay™ as an innovative and secure way to use your phone to make purchases with the touch of a finger.
Your [Token Requestor Name] Pay™ number is different than your debit card number.
To help keep your information safe, your device account number in [Digital Wallet Provider] Pay™ is different than the number on your debit card.
- You can see the last four digits of your debit card number and device account number in your Wallet at any time.
- The last four digits of your device account number will show on the receipt when you make a purchase.
- You can still use your [Issuer Name] debit card to make purchases.
If your phone is ever lost or stolen, you should notify [Issuer Name] by calling [Issuer Support Number]. If you or an authorized user didn’t request for your debit card to be added to [Digital Wallet Provider] Pay™, please call us at [Issuer Support Number].
Sincerely,
[Issuer Name]
Updated 9 months ago
Now that you are able to identify when cards are added to a Digital Wallet, you can build your apps to automatically send customized messaging to your customers through your preferred communication channel, helping to prevent fraud and ensure a sound customer experience.