What exactly the company reported

On September 24, 2026, EBANX issued an announcement about processing Apple Pay on its own infrastructure. The company dates the start of the rollout to September. Its documentation changelog already contains a description of two decryption models dated September 11: the September 24 publication does not establish the very first day the feature was available. [1 · EBANX · announcement on payment architecture and results, September 24, 2026] [4 · EBANX · documentation changelog, September 11, 2026 entry]

According to EBANX, the approval rate for tokenized-wallet transactions reached 94.4%, 11 percentage points higher than for conventional card payments. The sample size and a controlled comparison of the decryption models were not disclosed. These figures therefore cannot be presented as a proven increase attributable solely to moving the processing. [1 · EBANX · announcement on payment architecture and results, September 24, 2026]

What work remains for the online store

In the model where EBANX handles processing, the store passes an encrypted token without extracting payment credentials. The documentation describes availability in 11 markets in the region and retains an alternative model in which the merchant handles decryption itself. The choice concerns how control over infrastructure and keys is distributed. [2 · EBANX · two Apple Pay processing models]

The guide requires an active EBANX Direct integration, a merchant identifier and a certificate generated from an EBANX request. Setup on the provider’s side must be completed before the first transaction. Requests also retain country-dependent fields: a common technical method for passing the token does not remove local data requirements. [3 · EBANX · Apple Pay integration guide]

Expert commentary

The main practical question is how much payment complexity actually leaves the merchant’s team. Handing decryption to the provider can reduce the amount of in-house code and key maintenance. However, the store still has to configure the connection and remains responsible for a correct order. The offering should therefore be assessed as a redistribution of technical work among participants, rather than the complete removal of that work from the payment chain. [2 · EBANX · two Apple Pay processing models] [3 · EBANX · Apple Pay integration guide]

The published approval rate looks like a useful starting point for discussion, but a weak basis for forecasting revenue. Wallet users may differ from other shoppers in their devices, banks, baskets and readiness to complete an order. Even a persistent difference between the groups does not show that the new architecture itself caused the increase. Such a conclusion requires a separate, comparable experiment or a more detailed breakdown of transactions. [1 · EBANX · announcement on payment architecture and results, September 24, 2026]

The economics of integration are best tested through actual margin after fees, disputed transactions and refunds. Development hours, maintenance costs and the time needed to launch in the next market should also be considered. If those costs fall, the solution may pay for itself even without an increase in average order value. If pricing or dependence on a single provider rises, technical simplification will not necessarily become a commercial benefit. [1 · EBANX · announcement on payment architecture and results, September 24, 2026] [3 · EBANX · Apple Pay integration guide]

From a competitive perspective, this architecture could lower the integration barrier for a merchant with a small engineering team. The other side is the concentration of a critical function with an intermediary. Before expanding across several countries, it makes sense to check certificate-rotation procedures, investigation of declines and the ability to migrate. These are conditions for reliable operations, not evidence of flaws in a particular provider; the published description alone does not reveal their economic outcome. [2 · EBANX · two Apple Pay processing models] [3 · EBANX · Apple Pay integration guide]

What matters to the customer is completing a purchase and receiving clear help if a payment is declined, rather than where a cryptographic operation takes place. Better customer relationships are therefore possible only when payment, order records and support work together. The regional impact is also limited to users of compatible devices and cards. These figures do not support a conclusion that access to ecommerce has expanded equally for every social group or every country in the region. [2 · EBANX · two Apple Pay processing models] [5 · Apple · Apple Pay overview]

A testable scenario for the next one to three months is a limited integration with countries and banks tracked separately. The measures to watch are the share of successful payments, confirmation latency, retries, customer inquiries and the total cost of a completed order. If the improvement persists with a similar customer mix, there will be a basis for scaling the integration. So far, the description of an operating model and its provider’s metrics are established; independent assessment of the causes and durability of the effect remains open. [1 · EBANX · announcement on payment architecture and results, September 24, 2026] [3 · EBANX · Apple Pay integration guide]

Sources

  1. EBANX · announcement on payment architecture and results, September 24, 2026 — Primary company release. The metrics come from EBANX; the announcement date is not the date of the first launch.
  2. EBANX · two Apple Pay processing models — Official architecture and geographic coverage; checked September 26, 2026.
  3. EBANX · Apple Pay integration guide — Certificate, identifier and token-transmission setup; checked September 26, 2026.
  4. EBANX · documentation changelog, September 11, 2026 entry — Confirms that the documentation existed before the September 24 announcement.
  5. Apple · Apple Pay overview — Official description of the payment service and the supported user journey.