Digital Card Overview
- Casi Reily (Deactivated)
- Tiffany Rapp
Implementations - Dash Digital Customization Requirements - All Documents (sharepoint.com)
DIGITAL CARD
Primarily used for Reward and Disburse clients, a digital card product allows the cardholder to receive payment in the form of a ‘digital’ card sent to them via SMS or Email. These cards provide quick and efficient ways for clients to pay individuals when physical cards make less sense.
Like physical card fulfillment, issuance of a digital card can be done online in the PT Portal via:
Bulk batch file upload
Single card order
sFTP file drop
API (will return TinyURL)
Key determinations that must be established prior to onboarding are listed below.
Is this a Reloadable or Non-Reloadable card product?
Will PT control the delivery of the digital card?
If PT controlled, will delivery be SMS and/or Email?
Does the cardholder need a physical card option?
if so, who will cover the cost - client or cardholder?
Digital Customization
All Cardholder facing pieces/marketing must be approved by Pathward, which typically takes about 2 weeks. This includes:
Card Artwork
Email Template
Custom Splash Screens
Custom FAQ
Once Approved the Card Image, Email, Splash Screens, & FAQ can all be edited at the Customer Program Level. The Validation Method and T&C is set at the Product Level.
We can also customize the Subject Line and the ‘from’ email address that the digital email is sent from.
Specific information that Pathward requests to see in the email:
DIGITAL = Tokenized. Virtual = non-tokenized. Pathward is very particular about the verbiage that is used so update your templates accordingly.
From Email Address & Subject Line
Disclosure font should be 8pt
“Valid Only in US” should either be in Body of email or in disclosure (depending on subprogram)
“Card my be used for online and phone purchases only”
“No Cash Access”
Branded Digital cards should be squared, not rounded
TM symbol should be followed by first mention of Mastercard or Visa
Submit digital collateral for Pathward approval via the COLLATERAL REQUEST FORM
Redemption Details:
Whether PT controls the delivery or a client controls fulfillment, there are two ways to deliver the cards and ‘accesses to the account.’
Proxy
Proxy is a secure and unique card identifier received in the API response of a successful card order. This unique number would be dynamically communicated in the email delivery of the digital card.
User would copy the proxy, have it validated and then would be prompted to enter a piece of data they “know” (ie: custom Access Code, DOB, Last Name, etc.)
TinyURL
TinyURL is a custom URL that includes the proxy (hidden) that allows the cardholder to click the link and would immediately be dropped to the “Validation” entry screen. No manual proxy key entry step.
Users would be required to validate with a piece of information they “know” (ie: custom Access Code, DOB, Last Name, etc.)
The product setup in the portal determines the validation methods that can be used to access the digital card.
Payments products can use DOB, Last Name, or Last 4 of SSN
Reward products can use Last Name or 4 Digit Access Code (passed in SSN field)
Customers can use multiple authentication methods for additional security. For Example: Access Code & Last Name
Cardholder Website
MyDashCard
Our cardholder website and mobile application which allows a user to create a unique username/password combination to manage his/her account
Primarily used for reloadable programs
Card-Support
A cardholder website that allows a user to input a valid card number and validation method to access his/her card balance
No username/password combination and primarily used for non-Reloadable programs
Product has a VERY Detailed Digital & Physical Card document HERE
