Category: Merchant



Tech define bio-metrics in the payments context as ” a point-of-sale technology that uses bio-metric authentication to identify the user and authorize the deduction of funds from a bank account.”

Bio-metric payments today are typically generated through a mobile or wearable device and use two-factor authentication methods, such as personal identification numbers (PINs) and fingerprints, to qualify transactions. Most such devices are also equipped with contactless payment technology, which is designed to safely pass data from one device to another without the friction of entering numbers, swiping mag-stripe  cards or inserting (sometimes called dipping) smart cards.

Consumer adoption of bio-metric payment methods has been relatively slow. This is particularly true in the United States and other countries where card-based payments are still preferred. However, adoption of devices that employ bio-metrics is on the rise, and experts are predicting the widespread adoption of bio-metric payments will soon follow.

Now that embedded wallets and contactless payment capabilities are being built into bio-metric wearable, consumer curiosity  for bio-metric payments is likely to turn into market demand. However, the average merchant’s inability to accept payments made from biometric devises is a significant barrier. Even if today’s consumers were ready to adopt bio-metric payments more readily, they would still have to carry credit and debit cards, since so few merchants are ready to accept these payments.


Payment aggregation concept

Payment aggregation as a concept exists in two aspects covered below.

Straight aggregation

Historically payment aggregation was used to give payment processing capabilities to those businesses, which wouldn’t be able to go through merchant services underwriting otherwise. A central company (PSP) would get underwritten, have its own agreement with a processor and use the same MID to process (aggregate) payments of its smaller customers that wouldn’t go through individual underwriting and have their individual merchant accounts. The PSP would process all their payments and aggregate them through the central account, remit respective funds withdrawing its own fees.
Over time the credit card companies insisted on discontinuing this practice for the most part, as it was used for covering various illegal operations, such as drug sales, money laundering etc. As a consequence, the concept of a sub-merchant was introduced.

Sub-merchant funding

Under this concept each merchant goes through some form of underwriting, but the entire financial liability and risk is on the PSP and its entire portfolio. Instead of using one single MID for all merchants, each merchant is assigned its own MID, but this MID is linked to the portfolio of the PSP. Usually the PSP portfolio has much better processing rates than any member of the portfolio could have gotten on its own. PSP takes care of funding of merchant fees and statements.

Important aspects of payment aggregation model

Support for aggregation and remittance is an important enterprise feature, primarily targeted at PSPs. To facilitate efficient, transparent and flexible functioning of the payment aggregation model, resellers need to be able to perform a wide range of tasks. Particularly, a reseller, using payment aggregation model, needs to be able to do the following:

  • allow it to easily set up a merchant
  • process transactions on behalf of its multiple customers\sub-merchants
  • manage their accounts
  • use merchant-specific pricing
  • remit processing revenue back to merchants
  • withdraw merchant fees (transparently for the merchant)
  • generate statements (at the end of the month or on per-deposit basis)
  • share residual revenue with channel partners

To simplify each of these tasks, resellers need special tools. But not all processors/payment gateways are able to provide all the necessary tools to resellers. For instance, some are only able to back out their own fees, and some can not accommodate per merchant pricing.

In addition to the issues mentioned, several other considerations should be made. To learn about respective issues that PSPs should bear mind, please, consult the resources covering PCI compliance and credit card chargebacks on our web-site.

Square and PayPal are Aggregation Models.


VSR’s most recent report, State of the POS Market, delved into some of the leading reasons retailers are looking to upgrade their solutions. By keeping this in mind, developers can craft a compelling product that appeals to their target audience.

From the biggest priority to the least, here are some of the top reasons for upgrade:

1, Achieve PCI compliance (53 percent)
2, Integrate mobile POS support (49 percent)
3, Improve customer service and the overall experience (39 percent)
4, Increase speed of checkout (38 percent)
5, Real-time reporting to the main office (24 percent)
6, Enable new payment options, such as e-wallets (23 percent)
7, Tighter integration with e-commerce platforms (22 percent)
8, Enable omnichannel selling in stores (21 percent)