Does a direct scheme connection make the processor the acquirer?

Short answer

No. In the model Anne Willem de Vries describes, the processing platform does not become the acquirer. The bank or payment company keeps its scheme license and its role as acquirer, and uses the platform for processing. Direct-to-scheme changes the technical path a transaction takes to the network, not who holds the license or carries the risk.

In detail

No. In the model Anne Willem de Vries describes, the processing platform does not become the acquirer. The bank or payment company keeps its scheme license and its role as acquirer, and uses the platform for processing. Direct-to-scheme changes the technical path a transaction takes to the network, not who holds the license or carries the risk.

Two roles, often confused

The acquirer holds the scheme license, signs the merchant agreement, carries the financial and compliance risk, and settles funds. The processor moves the messages: authorization requests to the network, clearing files, responses back. Historically many acquirers outsourced processing to a third party, adding a layer between them and the network.

What direct-to-scheme changes

  • The processing platform connects to Visa and Mastercard itself, instead of through another processor.
  • Fewer hops mean faster certification of scheme releases and cleaner data on fees and declines.
  • The acquirer keeps its license, its merchants and its risk; it changes who carries its traffic.

Why operators care

A PSP or PayFac buying acquiring services wants to know how many layers sit between its transactions and the network, because each layer adds latency, a fee and a delay in adopting scheme changes. Asking an acquirer whether it processes directly is a fair due-diligence question. It does not change the contract: the acquirer remains the party responsible to the schemes and to the operator.

Still have a question?

Our team walks you through the platform with your use case on the table.

Book a demo