Control on virtual card transaction

[AbhiMineraltree]

I have one use case where we need to control the issued virtual card for the supplier to swipe the whole amount in a single transaction (Single swipe vcard) or allow the supplier to swipe multiple times till he gets the complete amount (multi swipe card)  (We are using B2B Virtual Account Payment Method)

Which API we can use to control this setting for each supplier?

[jenn_kh]

Hi, @AbhiMineraltree. Thank you for your question! Our agent is looking into this and will get back to you with more information soon. -Jenn

[API_Products]

Hi @AbhiMineraltree,

I recommend you to use Visa Token Services for the virtual card use case. Here's the link to the Visa Token Service API product:  https://developer.visa.com/capabilities/vts 

To learn more about Visa Token Service, please contact either your Visa Account Executive, Gateway or Acquiring partner and/or visit our detailed product page at Visa Ready. 

[AbhiMineraltree]

Hi Diana,

Already we are using B2B control functionality in our product now we just trying to add a new feature to make a virtual card as a multi-swipe card. I have gone through some documentation of VISA and I found out there are some rules that we can override but I need to understand the following conditions

1. which rule do we need to override to make multi swipe or unlimited transactions?

Can we override this rule for making cards multi swipe or a single swipe
{
"ruleCode": "SPV",
"overrides": [
{
"sequence": "1",
"overrideCode": "spendLimitAmount",
"overrideValue": "55.45"
},
{
"sequence": "2",
"overrideCode": "maxAuth",
"overrideValue": "10"
},
{
"sequence": "3",
"overrideCode": "amountCurrencyCode",
"overrideValue": "840"
},
{
"sequence": "4",
"overrideCode": "rangeType",
"overrideValue": "3"
},
{
"sequence": "5",
"overrideCode": "startDate",
"overrideValue": "05/11/2018"
},
{
"sequence": "5",
"overrideCode": "endDate",
"overrideValue": "05/20/2018"
},
{
"sequence": "7",
"overrideCode": "updateFlag",
"overrideValue": "NOCHANGE"
}
]
},

• If the card is single swipe then min & max amount to withdraw should be the same but if it is multi swipe min amount will be zero

// Is this proper rule which we can control on min value & max value
{ 
"ruleCode": "TOLRNC",
"overrides": [
{
"sequence": "0",
"overrideCode": "amountCurrencyCode",
"overrideValue": "840"
},
{
"sequence": "0",
"overrideCode": "minValue",
"overrideValue": "1"
},
{
"sequence": "0",
"overrideCode": "maxValue",
"overrideValue": "50"
}
]
},​

[API_Products]

Hi @AbhiMineraltree,

I'm checking with our product team so I'll get back soon. 

[API_Products]

Hi @AbhiMineraltree,

To allow multi-swipe, the Spend Velocity (SPV) rule will allow multi swipe up to the total amount as provided in the “Spend Limit Amount” override.  The “MaxAuth” override is where you can identify how many swipes are allowed. If it is zero or blank, it will be set to unlimited number of auths.  The cardholder can use up to the amount specified within the swipe and date parameters. 

For single swipe, where  “min & max amount to withdraw should be the same” then you can use Exact Match rule (VPAS) which allows a single authorization for that exact amount, to the penny.

[AbhiMineraltree]

Thanks for replying DianaTran,

I've another follow-up question about which service to use it. If I use the managed payment control then we are setting the ruleset against all virtual cards created under that account number/buyer id. I'm looking for setting up these rules at the supplier level (Some suppliers may opt for multi swipe cards and another single swipe card) how can we achieve this scenario. Do we have any service/control / API which we leverage to solve this scenario?

[API_Products]

Hi @AbhiMineraltree,

I'll ask our product team and get back soon. 

[API_Products]

Hi @AbhiMineraltree,

Manage Payment Controls API is used to manage the controls on a single account, not all accounts under the buyer. There is no bulk option with this API so each account must be modified individually. This is used for accounts provisioned through B2B Virtual Account Payment Method APIs.

There is another service, Visa B2B Payment Controls, that can be used to set authorization controls on an account provided by the client. Key is that the accounts for which the controls are being set must be accounts that were not provisioned through B2B Virtual Account Payment Method.

Here's the documentation link to the Visa B2B Payment Controls API: https://developer.visa.com/capabilities/visa-b2b-payment-controls