Visa+
A new service enabling both transfers between participating P2P payment apps and real-time payouts to participating apps.
How do you participate
Interested in offering Visa+ to your customers? Contact us: email [email protected] to get started and instantly push to all participating wallets!
For more information on how to integrate with Visa+, please check out our how to guide
About
A new service enabling both transfers between participating P2P payment apps and real-time payouts to participating apps.
- Expand your reach: Sending and receiving money traditionally meant both parties needed the same app. Visa+ changes that, offering a solution for transfers between participating payment apps.
- Simplify personal payments: Visa+ helps reduce the need for users to juggle multiple apps, accounts, usernames, and passwords. Now users can do more without leaving their preferred participating payment app.
- Help enhance privacy with Visa+: With Visa+, your users can get paid by sharing their Visa+ payname with others on a participating app — limit the need for them to give out their email addresses or phone numbers.
- Offer payouts to payment apps: Enrolled clients can use Visa+ to deliver real-time payouts to participating payments apps, offering gig workers, creators, and others, more destinations for their earnings.
Source: https://usa.visa.com/products/visa-plus.html
Using Visa+, you can instantly push funds to participating wallets using TabaPay's Unified API.
Give your customers the flexibility of payment options with Visa+.
Key Benefits:
- Real-time: Real-time payouts directly to any participating wallet. Real-time P2P for neo-banks.
- Data Security: Reduced data security and privacy risks. No need to capture Primary Account Number (PAN) and therefore no associated PCI obligations
- No IRF: No interchange on push to wallet payments
- Superior user experience: Easier for senders to provide a payment tag than entering recipient's card details!
Destination wallets are 'TabaPay Payment Tags' that have been issued by participating digital wallets or neo-banks.
How does it work
| Step | Description |
|---|---|
| 1 | Recipient shares payment tag with Sender |
| 2 | Sender enters recipient payment tag and amount in Client's acceptance application |
| 3 | Optional: Client confirms recipient's phone number. See confirm process below. (Optional, client will also receive the name associated with the payname). API Reference: Query Tag. |
| 4 | TabaPay client forwards request to TabaPay via Create Transaction API request. API Reference: Create Transaction. |
| 5 | TabaPay initiates instant push to the payment tag within the corresponding participating wallet provider |
| 6 | Funds instantly deposited in user’s payment tag linked payment card account |
| 7 | TabaPay receives confirmation about the instant push |
| 8 | TabaPay responds back to TabaPay client in the Create Transaction API response |
| 9 | TabaPay client displays payment confirmation to Sender. |
Confirm Recipient (Optional) using Query TagName
TabaPay Clients have the ability to optionally validate that an intended recipient’s phone number matches (or not) with the last 4 digits of the recipient phone number stored within the Visa+ database. Client will also receive the name associated with the Payname for further validations if necessary.
When to confirm?
TabaPay Clients can then provide this validation to the sender prior to completion of the payment.
It is up to TabaPay Clients to determine the criteria to prompt senders to conduct the confirmation. For example, clients may decide to confirm every time a user tries to send a payment to a payname for the first time or when the transaction amount exceeds a certain transaction limit. If the criteria is met, then the Sender can be prompted to confirm the recipient’s phone number.
This process is useful for reducing the risk of authorized fraud and incorrectly entered recipient information. Remember: this transaction type is irreversible, and you will not be able to retrieve funds back on fraudulent or incorrectly sent payments.
Confirmation Request in Query TagName API
For more information: Query Tag
TabaPay Clients who prefer to confirm a recipient provides the following information:
| Confirm - Request |
|---|
| (1) Payname |
| (2) Last 4 digits of the recipient's phone number |
Confirmation Response in Query TagName API
At the end of a confirmation request, TabaPay provides the following information to the client:
| (1) Result of Payname validation: Match, No match, Match not performed |
| (2) Recipient's Name |
Permitted usage of Recipient Name
When TabaPay Clients receive recipient's first/last name in the confirmation request, they must treat them with sensitivity.
While names can be stored, it must be treated as “moment in time” data.
How do you participate
Interested in offering Visa+ to your customers? Contact us: email [email protected] to get started and instantly push to all participating wallets!
Use cases
Users of participating digital wallet accounts or bank accounts can associate their stored valued accounts or payment cards to be associated with payment tags.
- Interoperable Person-to-Person (P2P) transfers: Senders can transfer funds to the recipient’s digital wallet account using the recipient’s Payment Tag through their payment app of choice that participates in this service, replacing the need for both sender and recipient to be on the same app.
- Funds Disbursement and payouts: TabaPay Clients can participate in the Visa+ Service as Payment Originators and send payments to the user’s digital wallet or stored value account at participating wallets via the Payment Tag instead of having to collect card or bank account information from the User.
Payments sent to payment tags will be delivered in real-time.
Participating players
Participating Wallets
The following Wallets participate in Visa+ and they are enabled to receive incoming funds instantly via TabaPay Create Transaction API
Payment Tags
Payment Tags issued by participating digital wallets or neo-banks are personalized, publicly shareable payment addresses for receiving funds and are often linked to a stored-value account.
- Digital wallets and neo-banks participating in Visa+ issue payment tags to their users
- Incoming instant push requests to TabaPay include these payment tags in our Unified API
- Senders of instant push payments to wallets are assumed to know the 'payment tags' of the recipient they intend to send funds to.
Payment Tag Format
Payment Tag Format
Payment Tags are issued by participating digital wallet providers. They enable their customers to create their own payment tag name.
+username.applicationdomain
e.g. +adam123.walletabc
| Requirement | Description |
|---|---|
| Prefix '+' character | Uniquely identifies Push to Wallet capability |
| payname | Usually defined by the user. Can contain numbers, letters, hyphen (-), and underscore (_) only. Maximum length 30 characters. Every payname is unique. |
| Delimiter: ‘.’ Character | Separates payname from the domain |
| Domain | Every participating wallet will have a specific domain name |
Underlying payment instruments
Payment Tags resolve to a unique Debit or General Purpose Reloadable Prepaid product.
Interoperability amongst Wallets
Visa+ allows a common Unified API to be used to send from any wallet to wallet as long as the originating and destination wallets are participating.
Best Practices for TabaPay Clients
- Store recipient payment tags: This allows clients to more easily access those recipient payment tags that are used most frequently. These functionalities can help consumers to avoid sending money to the incorrect person/payment tags.
- Request confirmation: Request that the sender confirm that the recipient’s payment tag is correct and that they are sending money to the correct person. TabaPay is not responsible for misspelt payment tags.
- Transaction notifications: Provide transaction notifications to inform the senders that the payment has been sent to the recipient.
Risk Best Practices for Visa+
- Unique Identifier: Plan to use a unique identifier passed from Visa to identify the Visa+ account in order to set controls at the ‘card’ level, as the payment tag itself can change. Restrict usage of the same Visa+ account across multiple user accounts for me-to-me use cases.
- Velocity Controls: Restrict the number and dollar amount of payments across various time periods at Visa+ account and user levels.
- Confirm the recipient: Utilize Visa’s Confirmation Request to validate the Last 4 digits of the recipient’s phone number with what the user has entered. Decline if no match exists. Ask the consumer to confirm the payment tag prior to proceeding with the payment.
- Pre-Authorization Fraud Rules: Risk score and approve/decline the transaction before submitting the payment.
- Account Takeover Controls: Ensure you have two-factor authentication, session monitoring, device intelligence, and/or risk scoring in place.
- Identity Theft Prevention: Utilize strong identity verification controls, such as selfie checks.
- Customer Education: Educate customers and add in warning messages within the user interface to ensure the customer knows the intended recipient.
Updated 2 months ago