Vietnam bank infrastructure · collection and payout

From 0.035%. One API, both ways.

DENO is a signed protocol for Vietnam bank transfer and VietQR. Fees follow monthly successful volume, and only the amount past a threshold takes the next rate. Above 200 billion dong, the agreed rate is 0.035%. From order to callback, more than 60% of collections finish within one minute, and 75% within two. Payout success is 100%. Release is measured in seconds, after the account number is checked against the name.

  • 01 Collection closes on a signed callback
  • 02 Payout in seconds, name matched to the account
  • 03 Bank app updates are absorbed by DENO

System

Collection closes cleanly. Payout is immediate, and exact.

These are the operating standards in production. Collection is measured from order to completed callback. Payout is measured by success rate and time to release.

60%+

Callback within one minute

Collection, from order to completion.

75%

Callback within two minutes

The same measure.

100%

Payout success

Settled as success.

Seconds

Payout timing

Released once accepted.

  1. 01

    Collection over API

    The integrating system opens the order. Arrival of funds closes it with a callback. Missed orders are rare, and nothing is re-entered by hand.

  2. 02

    Collection timing

    From the customer’s order to the completed callback, more than 60% finish within one minute, and 75% within two.

  3. 03

    Payout success, 100%

    Payout success stands at 100%. Unsuccessful items are not carried into the next day for a manual clear-down.

  4. 04

    Release in seconds

    Once accepted, a payout is released in seconds. It does not wait for a person to approve each line.

  5. 05

    Account and name

    Before release, the account number and the account name are compared with the order. A mismatch stops the payment.

  6. 06

    A protocol of our own

    DENO builds the protocol. When a bank application is updated, the rail is aligned to that version at once. The integration stays as it is.

  7. 07

    Bots, included

    Order lookup, balance, success and failure notices, and the end-of-day summary are included. They are not charged separately.

  8. 08

    Terms for scale

    A larger monthly commitment may set the rate, the settlement day, report columns, a branded page, and a private line. The integrator’s books stay as they are.

  9. 09

    Engineering response

    Integration, signatures, callbacks, and reconciliation are taken by engineers. Production events are ordered by impact, at any hour.

  10. 10

    Callback retry

    A notification that does not arrive is resent on an interval. Status may also be pulled, so both ledgers agree.

Pricing

0.035% at the floor. Only the overflow steps down.

The basis is successful amount in a calendar month, in dong. Volume fills the current band before any remainder takes the next rate. Amount already booked stays on its band. A refund returns the matching fee. Failed and reversed payments are not charged.

0.035%

Agreed floor

Above 200 billion dong of monthly successful volume, the overflow may be agreed at 0.035%. The first 10 billion remains 0.10%. The bands at 20, 50, and 100 billion apply only to the amount that crosses them.

Monthly successful volume Rate on that slice
Up to 10 billion 0.10%
10 – 20 billion 0.085%
20 – 50 billion 0.070%
50 – 100 billion 0.055%
100 – 200 billion 0.045%
Above 200 billion 0.035%
  • This schedule covers bank transfer and VietQR, for collection and payout. Card schemes and e-wallets are priced separately.
  • Published rates exclude VAT. Vietnamese service VAT is 10%. Whether it sits inside the price is a matter of contract.
  • 0.035% applies to an agreement with a monthly commitment, and not below upstream cost plus 0.015%. A shortfall is billed as the difference between the published rate and the agreed rate.
  • A per-transaction minimum may be agreed, so a small payment still covers its cost.

Worked examples

20 billion in a month

  • 10 billion × 0.10% 10.0 million
  • 10 billion × 0.085% 8.5 million

Fee VND 18.5 million

Effective rate 0.0925%

50 billion in a month

  • 10 billion × 0.10% 10.0 million
  • 10 billion × 0.085% 8.5 million
  • 30 billion × 0.070% 21.0 million

Fee VND 39.5 million

Effective rate 0.079%

100 billion in a month

  • First 50 billion 39.5 million
  • 50 billion × 0.055% 27.5 million

Fee VND 67 million

Effective rate 0.067%

Protocol

One signature. Two ledgers.

Each request carries a timestamp, an idempotency key, and a signature. A replay is rejected. Collection closes on a callback, and a miss is retried. Payout checks the account number against the name before release. Fields and the algorithm are in the integration document.

Collection

  1. Open a collection with amount, bank, and merchant reference
  2. Receive the account or the VietQR for the payer
  3. A callback follows settlement. More than 60% complete within a minute; a miss is retried

Payout

  1. Submit account, name, bank, and amount
  2. A mismatch between account and name is refused
  3. Release is in seconds. One idempotency key pays once

Banks

Several banks. One protocol.

An order may name the bank. ACB, VCB, VPB, Timo, and the others share one request. If a bank is in maintenance, or tightens its limits, the order moves to a reserve path. The merchant reference does not change. When a bank application is updated, DENO aligns the rail first.

ACB Asia Commercial Bank
PVCB PVcomBank
HDB HDBank
STB Sacombank
VCB Vietcombank
EIB Eximbank
VPB VPBank
SHB SHB
TIMO Timo

The other connected Vietnamese banks use the same protocol. Where volume sits on one bank, that bank may be set as the preferred path.

Reliability

Books that match. Payments to the right account.

Collection is confirmed when the callback arrives. Payout is confirmed when the account matches the name. The day closes on a file that can be checked line by line.

Idempotency

A retry after timeout uses the same key. A shaky network produces one payout. A resend is not a second payment.

Callback retry

A notification that misses its destination is resent on an interval. Status can also be pulled, so the local record matches the rail.

Account check

Payout compares account number, account name, and order. A mismatch stops before release.

End-of-day file

Success, refunds, and fees are listed apart. The next day, the file reconciles the system to the bank, line by line.

Custom

The standard protocol is enough. Scale is written into the agreement.

The bots are included. Rate, settlement, reports, and network boundaries are set out in the agreement for larger volume. The integrator does not rebuild a ledger to fit a generic document.

Agreed rate

A commitment above 200 billion a month may be agreed at 0.035%. A shortfall is trued up. Settled months are not rewritten.

Settlement

Settlement day, reserve ratio, and the way a refund reverses a fee are written into the contract.

Callbacks and files

Callback fields, the place of the signature, the retry count, and the encoding and column order of the reconciliation file can follow the posting program already in use.

Signing and network

An IP allow list, a key-rotation cycle, and a fixed egress or private line are set to the security requirement. Keys are not written to logs.

A branded result page

The path remains the API. Where a payer should see a result in the integrator’s own name, that page can be added.

Bots

Order lookup, balance, success and failure notices, and the end-of-day summary are included, and not priced apart.

Contact

Integration begins with a conversation.

Telegram and email are how DENO is reached. Scope, bank paths, and the fee agreement — including 0.035% above 200 billion — are settled there.

Card schemes and e-wallets are priced separately.