Payment Gateway North Macedonia: how online card payments actually work

When a customer enters a card and presses Pay, the screen makes it look like one operation. In reality, checkout, the payment provider, acquiring infrastructure, the card network and the issuing bank exchange information within seconds.

That is why a payment gateway should not be judged by transaction fee alone. The merchant needs to understand supported markets and cards, authentication, risk, refunds, disputes, currencies and—most importantly—how payment status becomes an actionable order.

What is a payment gateway?

A payment gateway is part of the infrastructure that securely transmits the information required to initiate payment authorization. Modern providers can combine gateway, processing, acquiring and other payment services behind one integration layer.

For an ecommerce business, the useful operational questions are whether payment succeeded, which order it belongs to, whether authentication is required, when funds become available and what happens when a refund or dispute appears later.

What happens after the customer presses Pay?

3D Secure, fraud and why a valid card can still be declined

A decline does not automatically mean the customer lacks funds or that the store is suspicious. The issuer can decline based on authentication, card restrictions, incorrect details, its own risk rules or other signals. 3D Secure adds another authentication layer when required.

A foreign card is not automatically treated as spam because the merchant is based in the Balkans. Cross-border authorization can have a different risk profile, but the outcome depends on multiple participants and signals across the payment chain.

Local bank gateway or global payment provider?

A local gateway can be an excellent fit for a business focused on its domestic market. A merchant planning multiple markets, currencies and cross-border cards should also compare acquiring coverage, developer tooling, risk controls, refunds, disputes and operational visibility.

There is no universally superior provider. The right infrastructure depends on the business model. Kordiva's position is therefore not that local banks are bad; the question is whether the payment and commerce architecture fits where the business intends to sell.

Payment success is not the end of an order

A successful payment should trigger an organized process: correct order status, inventory changes where applicable, fulfilment work, customer confirmation and a traceable path for a later refund or dispute.

A payment confirmation, order confirmation, invoice and fiscal receipt are not interchangeable documents. The merchant must apply the appropriate North Macedonian fiscal and business-document rules for its transaction model.

How Kordiva connects payment with the complete commerce flow

Kordiva is the commerce layer around the payment. A merchant can use a professional Next.js storefront, checkout links for social selling or an API integration for an existing website, while products, variants, inventory, orders and operations remain connected through the CMS.

For supported registered businesses in North Macedonia, Kordiva connects merchants to Stripe Connect onboarding. Stripe performs its own verification and makes its own eligibility decision; Kordiva cannot guarantee Stripe approval. Kordiva also applies its own compliance and risk policy to the organizations, products and business models permitted on the platform.

Kordiva is also preparing local e-Invoice integration around the Public Revenue Office system. Until the official production interfaces and rollout are available, this should not be represented as a completed production government integration.