The purpose of the Card Acquiring chapter is to guide you through the various aspects of Evolve's Acquiring services.

What is Card Acquiring?

Card Acquiring is a solution for sponsoring and processing debit and credit card transactions. Our solution supports single transactions or tokenized card storage for repeat transactions. We support push to card transactions in addition to traditional pull/purchase transactions, RPPS and cash pick-up for Customers.

Acquiring Terminology:

Below are some common terms used throughout our Acquiring documentation. It is important to note that the customer type is important when discussing Acquiring. Merchant services vs. Fintech services may differ for this solution.

Card Acquiring Processing - API solution for processing card not present debit and credit transactions. Supports single transactions or tokenized card storage for repeat transactions. Also supports push to card transactions in addition to traditional pull/purchase transactions.

(GRAPHIC HERE)

Network Sponsorship (Sponsoring) - In order to gain access to debit, credit, or ATM networks, Customers must be sponsored in by a bank; Once they are sponsored into a network, the Customer can use programs that leverage the network's resources.

Processing + Sponsoring - In addition to sponsoring Customers into the major networks, Evolve can also serve as the Processor for transactions. As a Processor, Evolve is responsible for:

Providing Platform with resources to collect card payment data (POS System/ Card Machines or Payment Gateways)
Authorize transaction and verify card holder funds with Issuer Bank via Network at the time of transaction
Settlement of funds between Issuer Bank and acquiring Platform Bank (Evolve)
Transfer of funds and fees from Issuer Bank to Processor, Platform Bank (Evolve), and Platform

Card Acquiring Solutions

There are 4 solutions in our acquiring stack:

1. Purchase ("Pull") Transactions
Represents a traditional card purchase transaction (or "Pull" transaction), usually through a Point of Sale (POS) or eCommerce application. The End User's card and verification data are collected by the Platform and used to initiate a pull transaction across one of the card networks. The data is verified and processed through Evolve.

Available for Fintechs & Merchants

2. Push to Card
Push to Card facilitates the delivery of funds quickly and securely to both card and non-card endpoints, including bank accounts, mobile wallets and cash-out locations. Push facilitates the delivery of funds for all debit cards, credit cards and prepaid cards. A disbursement is not linked to any purchase. We support Visa Direct, Mastercard Send and all regional networks.

Available for Fintechs & Merchants

3. Remote Payment & Presentment Service (RPPS)
Remote Payment & Presentment Service (or RPPS) is a method of paying bills to about 95% of industry service providers in the U.S. through an electronic payment network. This solution provides customers one-stop access to comprehensive electronic routing, settlement services, billing, and online research tools. Evolve must both sponsor and process RPPS for our FinTech partners.

Available for Fintechs

4. Mastercard Cash Pick-Up (MCCPU)
Cash Pick-Up enables End Users to instantly access cash at any enabled ATM using only their phone number and transaction code to receive funds. A credit/debit card, bank account or mobile app is not
required for pickup. Evolve must both sponsor and process Cash Pick-Up for our FinTech partners.

Available for Fintechs

Card Acquiring APIs

The Evolve Card Acquiring APIs provide access to Evolve endpoints to help you onboard users, add nodes (eg. bank account, deposit account or domestic/international wire sources) or create transactions.

This version of the API is architected around REST using standard HTTP verbs to communicate and HTTP response codes to indicate status and errors. All responses come in standard JSON (unless the application is down).

Test API Endpoint: https://apitest.getevolved.com/v1
Production API Endpoint: https://api.getevolved.com/v1

Please see the Acquiring section of our API References for more details. You can download the OpenAPI Specifications `here.