With the growing demand for white-labe payment cards, companies should know how to choose a card issuance API that will best provide them with all the features they need to maximize the value of these cards.
Traditional banks, neobanks, retail and e-commerce companies, businesses in the gig economy, and various other corporates have embraced white-label payment cards – debit cards, credit cards, payroll cards, virtual cards, and expense cards – for a variety of reasons:
- Employee rewards
- Sales incentives programs
- Customer loyalty programs
- Employee expense management, among others.
These white-label cards have provided a wide range of benefits including positive brand image, improved brand awareness, higher customer loyalty, and greater employee retention. Because of these advantages, it is not surprising that usage continues to grow.
However, enjoying the benefits of white-label payment cards require that corporations choose a card issuance API that is simple and easy to integrate while also providing the following benefits:
- Excellent functionality
- Versatility
- Security and fraud prevention
- Regulatory compliance
- Analytics and reports
All of these and more are what Berkeley Payment’s card issuance API provides.
In this article, we will highlight the benefits that Berkeley Payment provides and how you can easily integrate its API so you can start issuing physical or virtual payment cards for your business.
[Do you want to create white-label cards that will boost your brand? The Berkeley Payment card issuance API will help you get started in a simple and seamless way. Contact us to learn more about how we can help you.]
5 benefits of integrating Berkeley Payment’s card issuance API
Excellent functionality
The ability to customize and personalize is at the heart of the benefits that white-label payment cards provide.
With Berkeley Payment, you can choose from more than 300+ features to customize your cards in a way that best promotes your brand.
Apart from design elements, you can choose to allow ATM withdrawals, select virtual and/or physical cards (as well as choose between Visa and MasterCard), pick the customer verification system you desire, and even elect to make your cards multi usable.
Versatility
We have a large pool of customers who use our cards for various reasons – salesforce rewards, employee rewards, customer loyalty programs, among others.
Similarly, some choose non-reloadable cards while others opt for reloadable cards. We also provide all types of white-label cards: debit cards, prepaid cards, expense cards, payroll cards, among others.
Like other cards, you can use these cards for offline and online payments in any marketplaces of your choice.
Security and fraud prevention
We use multi-tenant architecture and PCI certification to protect you from cyberthreats. We also use encryption, PCI compliance, and automated payment activity review to prevent card frauds.
Regulatory compliance
With more than 17 years of experience, we have worked with companies from various industries in North America. We comply with all relevant regulations guiding our operations and that of the clients we serve.
It is why top companies like Coca Cola, Google, Nestle, Mercedes Benz, Foresters Financial, Kraft, among others have trusted us with their payment needs.
Analytics and reports
The only way to make better decisions is to gain access to relevant data. Berkeley Payment provides clients with data that can be turned into insights regarding the usage of their white-label payment cards.
How to seamlessly integrate Berkeley Payment’s card issuance API in 7 steps
To make it easy for all types of businesses to use Berkeley Payment, we have made our card issuance API as seamless and streamlined as possible.
You can get started in just few steps:
1. Acquire authentication
All activities involving the integration of the Berkeley API will take place through the base URLs in the image below.
Initial access will be given to you after the customer onboarding process.
While working on the API integration, you will also need to get public and private tokens (as well as temporary keys) for authentication.
2. Card creation and issuance
To issue cards, you will need to start with the Card Issuance endpoint which can be accessed through a POST request using JSON.
Creating cardholders
To create new cards, however, you must first create cardholders. Every card created will be attached to a previously created cardholder.
Below is a sample list of cardholders for a user:
For physical cards, you will need to add the shipping details of the cardholder so the card can be delivered. Physical cards can be sent on-demand or you can ship them in bulk.
Also, every cardholder must be associated with a particular program (customer loyalty, employee rewards, etc.).
Verifying cardholders
As part of our security system, we will conduct a CPI/KYC verification before card issuance. The steps involved are specified in the workflow below:
Creating and activating cards
Once you have created a cardholder, a card will be created for the cardholder. You can also select a cardholder and create more cards for the holder.
For physical cards, you will find card details (card numbers, CVV, expiry date) that will be needed to activate the card before it can be used. Below is an example of the card activation page:
Create card pin
Cardholders can create pins in three ways:
- IVR: They can call an automated phone system to set the pin.
- CSR: They can call customer care to set and change card pins.
- API: They can use the Set Pin endpoint to set a new pin.
Card management (modify cards)
You can also activate, suspend, or mark cards as stolen or lost. For the latter, cardholders can automatically request for a replacement card.
3. Creating financial accounts and external accounts
Every cardholder will have a financial account associated with them. A cardholder may have more than one account and one account can be associated with multiple cards.
Below is an example of a cardholder with one account and one card:
Cardholders can also add external accounts (traditional bank account or a digital wallet provided by a fintech company) created outside of the system.
4. Creating value loads and unloads
After creating cardholders and cards, you can load money into any of the cards created.
You can do this through the Value Load endpoint.
Below is an example of a Berkeley Payment user who has created two value loads worth $1,500:
For spending controls, you can create spending limits for each card program which will set a boundary for the amount you can spend on value loads associated with that program.
Using the same endpoint, you can remove funds from any card through what is called Value Unload.
5. Card to card transfers and external transfers
Card to card transfer is the movement of funds from one cardholder to another cardholder within the Berkeley Payment system.
Funds can also be transferred from a cardholder to an external account, what is called an external transfer.
Both transfers can be accessed through the Card Issuing endpoint.
6. Transferring money with DirectSend
Instead of going through the Card Issuing endpoint, you can also make disbursements to financial accounts through the DirectSend endpoint.
DirectSend is a real-time payment mechanism on Berkeley Payment. Transfers can be completed within 30 minutes and you will be provided with regular updates on the status of the transfer.
Below is an example of a transfer done through the DirectSend endpoint.
Just like the value load and value unload under the Card Issuance endpoint, there are two use cases for DirectSend:
- Pull transactions: A pull transaction debits a particular amount from a financial account.
Push transactions: A push transaction credits a financial account with a specific amount.
7. Get access to quality reports
Through the DirectSend endpoint, you can gain access to detailed reports about the money you have spent on each program.
This report will help you make better decisions regarding your current and future programs.
[For more technical information on how to integrate our card issuance API, please read our API docs. You will also find user guides, technical guides, and answers to FAQs]
Start issuing physical or virtual payment cards with Berkeley Payment
Berkeley Payment, in addition to providing the features you need to maximize the value of white-label payment cards, has also implemented a seamless card issuance API that is easy to integrate with any preexisting system.
If you want to quickly get started in a cost-effective way while ensuring security, compliance, versatility, excellent functionality, and timely reports, then Berkeley Payment is the partner you can trust.
Whether it is physical or virtual cards and whether it is for corporate rewards or customer loyalty programs, Berkeley Payment has everything you need to create quality programs. The quality of companies that have worked with us for the past 17 years is the proof you need of our competence and expertise.
[Do you want to create and issue white-label payment cards for your business? Contact Berkeley Payment to learn more on how we can help you improve brand awareness, customer loyalty, and employee retention with our card issuance API.]
