Looking to free up time for your payments team and whitelist cards faster to increase deposit acceptance rates?
Every payment provider has their own set of rules and processes that a Payments team has to follow. This often leads to lengthy daily manual processes for tasks such as whitelisting cards.
That is where Flows comes in, providing an easier, faster and more efficient no-code workflow for you and your teams.. With Flows you can automate these processes fully – adhering to each Payment provider’s set of rules and processes such as the format of the account numbers, and when and where to get the list for whitelisting.
All you need to do – Just Flow it!
How do you Flow it?
Trigger, route and get the transaction details - it’s that simple!
Start your Flow by selecting the trigger, in this example the trigger is on a Deposit.
The Flow then checks if this is a successful deposit using a Credit Card and proceeds to call the payment IQ to retrieve the PAN (Primary account number, for example 123456******7891). Remember that you can easily integrate with any payment platform using Flows.
Get further account information and send for Whitelisting
The flow continues on the green path after getting the transaction details. We then check if this was the first successful deposit for that specific PAN, which would ensure that it has not been whitelisted before.
The PAN is then sent via email to the payment provider for whitelisting so that everyone with that PAN can now use this payment provider.
With Flows you can also easily send via Slack, directly via an API to the payment provider, or whatever form the provider would like to receive the PANs for whitelisting. Flows allows you to adapt easily to each Payment provider’s requirements without all the manual work, saving you a lot of time and frustration.
How do I edit the PAN format and send?
Here in this example we are changing the format of the PAN from 123456******7891 to 123456+7891 before sending for whitelisting using a Regex split for the numbers and simply adding a plus inbetween.
Can I send the PANs as a list multiple times per day?
Some payment providers prefer to get the PANs for whitelisting once or twice per day in a list. With Flows innovative no-code platform you can easily adapt to all requirements.
In our Flow example shown here above, we add and store a list (comma separated) of the PANs for use later in our Flow.
So how do we do this? Well, after saving the lists, we set up wait times for when the lists should be sent every day. In Flows, the blue path follows after the wait and the green follows immediately. In this example we have two different paths as the list should be sent twice daily. We also add a lock so the list is only sent once per set wait time, instead of once per triggered flow (once per deposit).
Here the flow continues after the set waits, we get the lists of PANs that we saved earlier and send via email for whitelisting. After each send, the list is deleted so the same PANs are not sent again.
And there you have it, it really is that easy to automate your digital process using Flows, without a single line of code, just think it and Flow it!
