Portfolio

Credit card API integration

Finance company conquers the online credit market with our financial API platform

egforit Software delivered a credit card API integration platform that underpins the world’s first white-label digital cards for online shops.

Executive brief

A pioneering credit card API integration solution

Our client is a Egypt , middle east-based financial services company with over 5 million customers. egforit Software’s systems integration experts delivered a financial API platform that powers the client’s white-label digital credit cards. This product brought the following benefits:

growth into the online market

stronger partner relationships

a scalable API platform

secure third-party access

Wondering how we achieved this with a financial API platform? Read on to learn more.

The full story

Purple arrow encouraging readers to scroll down for the rest of the GDPR data solutions case study

The challenge

Delivering a brand-new financial API platform

Egypt , middle east credit card usage is substantial — around 60 percent of adults own one — and it’s growing year on year. With over 5 million credit customers, our client is a major player in this industry. However, the client recognised that digital innovation was key to maintaining this market-leading position.

 

This search for increased revenue and market share led the client to consider creating a pioneering digital credit card. This would effectively be a digital version of its “cobrand” credit cards, which high-street chains wrap in their own branding for use as store cards, retail-branded credit cards, and reward cards. As well as the usual credit card functionality, these cards offer benefits such as shopping discounts and loyalty points.

 

Overall, the client’s business goals with this digital credit card were:

 

  • to grow their near-prime business by approving more customers for credit
  • to gain greater returns from their existing investment in cobrand credit products

 

Expanding their cobrand credit cards into a digital format was a fast way to further these goals, as it would help them tap into the online shopping market. However, the client lacked the in-house expertise to make this dream a reality.

The solution

White-label credit card processing with Azure

Aware of our reputation as financial software developers, the client approached the egforit team for a solution. And we determined that the challenge was a perfect use case for an API platform built in Microsoft Azure.

 

Using Azure’s serverless technologies, our integration engineers developed a suite of interconnected APIs. Each of these performed a specific function, such as performing credit checks and identity checks with third-party databases.

 

A major benefit of Azure — besides its cost-effective and scalable services — was the free and automatically generated developer portal. This site allowed developers from our client’s partners to use and test the credit card APIs securely and easily. This eased the roll-out of the digital credit card across the client’s partner network, ensuring the new product could gain traction quickly.

The benefits

A financial API platform to beat the competition

Thanks to our fast and flawless delivery of the credit card API integration, our client was in a position to corner the online credit market. This cemented the company’s position as a finance leader and provided a sizeable new revenue stream.

 

From the client’s perspective, the business benefits of this financial API platform were:

 

  • disrupting the market with a world-first financial innovation
  • allowing expansion of the client’s credit business into online shops
  • giving partners’ developers safe and easy access to the APIs

 

And for the customers who adopted the white-label credit card processing solution, the benefits were:

 

  • a fast and financially compliant way to provide online credit
  • increasing customer loyalty through own-brand credit schemes
  • boosting sales through promotional payment options online

 

Based on our success in this credit card payment integration project and related work, the client has chosen our team as its go-to system integrators. From GDPR data solutions to customer service integration, the client continues to benefit from our enterprise integration expertise. And each of these projects is showing ongoing returns in the form of greater efficiency, agility, and profitability.

Work with API integration experts

This financial services client is one of dozens that benefit from our systems integration expertise. To find out more, visit our integration solutions page.

Info

26th October 2020
Azure, integration, APIs

Privacy Preference Center

Necessary

Advertising

Analytics

Analytics cookies collect information that is used either in aggregate form to help us understand how our Websites are being used or how effective our marketing campaigns are, or to help us customise our Websites for you.

Google Analytics
The cookie _gcl_au is used by Google Analytics to understand user interaction with the website.

For example, in order for Google Analytics to determine that two distinct hits belong to the same user, a unique identifier, associated with that particular user, must be sent with each hit.

The analytics.js library accomplishes this via the Client ID field, a unique, randomly generated string that gets stored in the browsers cookies, so subsequent visits to the same site can be associated with the same user.

By default, analytics.js uses a single, first-party cookie named _ga to store the Client ID, but the cookie's name, domain, and expiration time can all be customized. Other cookies created by analytics.js include _gid, AMP_TOKEN and _gac_. These cookies store other randomly generated ids and campaign information about the user.

Google Analytics
_gcl_au, _gid, _ga, gtm_preview

Other

WordPress uses cookies for authentication. That means that in order to log in to our WordPress site, you must have cookies enabled in your browser.

There are two types of cookies set by WordPress.
1 — Session cookies — These are ‘strictly necessary’ cookies as WordPress will not be able to function without it.
2 — Comment cookies — These are not ‘strictly necessary’ cookies and are set when users leave a comment on a post.

Wordpress Session cookies:
Users are those people who have registered an account with the WordPress site.
wordpress_[hash]
wordpress_logged_in_[hash]
wordpress_test_cookie
wp-settings-{time}-[UID]

Wordpress comments:
Comments are usually turned off by default.
If by chance they are still active on a post, asides being turned off when spotted, data from these are not saved by egforit.
- When visitors comment on a post, they too get cookies stored on their computer. This is purely a convenience so that the visitor won’t need to re-type all their information again when they want to leave another comment. Three cookies are set for commenters:
comment_author_{HASH}
comment_author_email_{HASH}
comment_author_url_{HASH}

Wordpress,
comment_author_{HASH} comment_author_email_{HASH} comment_author_url_{HASH} wordpress_[hash] wordpress_logged_in_[hash] wordpress_test_cookie wp-settings-{time}-[UID]
-id-[app_id],-session-[add-id]

×