Anatomy of a payment: where your 250 dinars go in 3 seconds

You click "pay." The button turns grey. A spinner appears. Three seconds later: "payment successful." You close the tab and forget about it.

But in those three seconds, your 250 dinars just went on a road trip through five organisations, two countries, and a small mountain of compliance checks. Here's where every dinar went.

Meet the players

Before we trace the money, let's meet everyone at the table. Think of it as a heist movie, except nobody steals anything — they all take a small cut.

You (the customer) — holding a Visa card issued by your bank.

The online store — selling coffee for 250 RSD. They just want the money in their account.

The payment gateway (that's us, Polako Finance) — the connector between the store's website and the banking system. We create the payment session, show you the payment page, and route your transaction.

The acquiring bank — the bank that processes card payments on behalf of the merchant. They have a contract with Visa/Mastercard to accept card transactions.

The card network (Visa, Mastercard, or DinaCard) — the rails. They don't hold anyone's money, but they route the message "this card wants to pay this merchant this amount" between banks.

The issuing bank — your bank. The one that gave you the card. They decide whether to approve or decline the transaction.

For a child: imagine buying a toy from a street vendor. You hand money to your parent (issuing bank), who gives it to the market manager (card network), who passes it to the vendor's helper (acquiring bank), who used a special cash register (payment gateway) to ring it up, and finally the vendor (merchant) gets the money — minus a small fee each helper kept.

The three-second journey

Second 0.0 — You click "pay"

Your browser opens the Polako Finance payment page. When you enter your card details, they go directly to the acquiring bank's secure processing system — Polako Finance never sees or handles your card number.

Second 0.3 — Authorization request

The acquiring bank packages your transaction into a message and sends it to the card network (Visa/Mastercard). The message says: "Card ending in 4242 wants to pay 250 RSD to Coffee Shop SRB."

Second 0.8 — The network routes

Visa receives the message, identifies your issuing bank from your card number, and forwards the request. This happens through a global network that processes 65,000 transactions per second worldwide.

Second 1.2 — Your bank decides

Your issuing bank checks: Does this card exist? Is it active? Is there enough balance? Is this transaction suspicious? Does it match your spending patterns? Is the merchant on any block list?

If everything checks out: APPROVED. If not: DECLINED, with a reason code the merchant never shows you ("insufficient funds" is the polite one; "suspected fraud" is the awkward one).

Second 1.8 — The response travels back

Approved. The response goes back through Visa → acquiring bank → Polako Finance → your browser. "Payment successful."

Second 2.5 — Fiscal receipt

In Serbia, the law requires a fiscal receipt for every transaction. The payment gateway triggers eFiskalizacija — a digital receipt is generated and registered with the tax authority. This happens in the background before you even see the confirmation page.

Second 3.0 — You see "success"

The whole journey — card validation, fraud check, bank approval, fiscal receipt — in under three seconds.

But your money hasn't actually moved yet.

When the money actually moves (it's not instant)

The "payment successful" message means your bank has reserved 250 RSD on your card. The actual money transfer happens later, during settlement.

T+0 (same day): The acquiring bank batches all approved transactions and sends them to the card networks for clearing.

T+1 (next business day): The card network calculates who owes whom and initiates the actual fund transfer between banks.

T+1 to T+7: The merchant's acquiring bank receives the funds and credits the merchant's account. The exact timing depends on the acquirer's schedule and the merchant's contract.

So when you paid 250 RSD for coffee on Monday, the coffee shop might see the money anywhere from Tuesday to the following Monday. For the customer, it feels instant. For the merchant, it's a 1–7 day wait.

DinaCard: the local shortcut

When you pay with DinaCard (Serbia's domestic card scheme), the journey is shorter. There's no international card network — DinaCard transactions stay within the Serbian banking system. The issuing bank and acquiring bank communicate through the NBS clearing system.

Result: faster settlement and a fully domestic processing chain. It's one reason DinaCard remains popular with Serbian merchants.

What can go wrong (and does)

Decline without reason. Your bank says no, but the error message just says "payment failed." Could be insufficient funds, a spending limit, a fraud flag, or your bank's system being down. The merchant and payment gateway can't tell you which — the bank keeps it vague for security reasons.

Currency conversion surprise. If the merchant charges in EUR but your card is in RSD, your bank applies its own exchange rate plus a conversion fee (typically 1–3%). Always pay in the merchant's currency when given the choice.

3D Secure authentication. That extra step where your bank asks for a code or biometric confirmation. It adds 5–10 seconds and some friction, but it's what keeps stolen card numbers from working. Since DinaCard Secure launched, this applies to domestic cards too.

In short

• Your payment touches 6 parties in under 3 seconds: you, merchant, gateway, acquirer, network, issuer
• The actual money arrives 1–7 business days later via settlement
• DinaCard keeps it local — shorter route, faster settlement
• That "payment successful" message is actually a promise, not a transfer — the real money moves overnight