VISA Card Payouts
Solution Overview
- Payout Instrument: VISA Debit Card
- Payment use cases:
- Peer to Peer
- Business to Peer
- Business to Business
- Supported Destination Markets: Fast fund enabled markets (43 markets)
- Network Speed:
- Realtime payment processing
- Availability: 24x7
- Solutions Available
- API Integration
- Infrastructure for both: PCI Compliant and PCI Non-Compliant clients
Solution for PCI Compliant Clients
- PCI Compliant clients may manage the card data within their own systems
- The clients only need to share the encrypted card details as part of the payment instruction itself
- The encryption of the card is done via the public key shared by NIUM
Data Flow
The encrypted card number is to be shared as part of the payment instruction in the field - beneficiary.encrypted_card_number
Solution for PCI Non-Compliant Clients
- The client, being non-PCI compliant, cannot accept the VISA card details from the Reme
- NIUM, being PCI Compliant, shall provision the infrastructure to collect the card data from the Reme in a secure manner
Basic Flow:
- Remitter intends to make a payout to a beneficiary, to a VISA card number
- Client calls NIUM's system (API) to get a secure "Form" wherein the Remitter can share the card details
- The card details are directly routed to NIUM, w/o any passage through client's system, and are validated
- In case the card details are valid, NIUM shall send card meta-data (masked card number and card token) to the client(host application)
- Client can save the card meta-data shared and use the card token as a reference to the actual card information for the future payment instructions
Card Data Flow
Implementation
The client needs to add the following listener to receive messages:
window.addEventListener('message', (event) => {console.log(event.data)}, false)
Information shared once the card is tokenised
{
"message": "cardData",
"value": {
"token": "759e02c8-e62e-40f7-804c-430a46bbaeb9",
"metadata": {
"cardTypeCode": "C",
"billingCurrencyCode": "VND",
"billingCurrencyMinorDigits": "0",
"issuerName": "INTL HDQTRS-CENTER OWNED",
"cardIssuerCountryCode": "VN",
"fastFundsIndicator": "N",
"pushFundsBlockIndicator": "Y",
"onlineGambingBlockIndicator": "Y",
"isCardValid": true,
"maskedCardNumber": "XXXX XXXX XXXX 0018",
"cardToken": "759e02c8-e62e-40f7-804c-430a46bbaeb9"
}
}
}
Payment Instruction Flow
Data Flow
The tokenised card information is to be shared as part of the payment instruction in the field - beneficiary.card_token