OneFin VietNam

OneFin VietNam: Payment Acceptance Overview For Merchants

OneFin VietNam operates a payment acceptance stack that supports both online and in-person checkout use cases in Vietnam. For merchants, the product set spans a payment gateway for web and app payments, QR-based payment flows for on-site and digital commerce, and device-led acceptance options such as SmartPOS and Tap to Phone. The platform also provides a documented API flow with callback handling, transaction status querying, and a hosted payment page model for redirect-based checkout.

OneFin VietNam Payment Acceptance Stack

OneFin’s merchant-facing offering can be grouped into three core acceptance layers:

• Payment gateway and hosted checkout for online payments

• QR code payments for in-store and digital commerce flows

• In-person acceptance via SmartPOS and Tap to Phone (NFC-based contactless acceptance on a phone)

In addition, OneFin positions its broader ecosystem around electronic payments, e-wallet functionality, and integrations intended to fit into a merchant’s existing app, website, or POS environment.

Online Payment Gateway And Hosted Checkout

For online acceptance, OneFin provides a payment gateway flow where the merchant server creates a payment request, receives a redirect URL, and sends the customer to a OneFin payment page to complete payment.

Typical Flow For A Hosted Payment Page Checkout

A common OneFin integration pattern uses a hosted payment page design:

1. The merchant initiates a payment request to OneFin.

2. OneFin returns a payment URL.

3. The merchant redirects the customer’s browser to that URL to complete payment.

4. OneFin returns results using a merchant callback endpoint and then routes the customer back to the merchant’s response page.

This structure is consistent with a redirect-based checkout model and can reduce the merchant’s scope for handling sensitive payment input directly, depending on the selected payment method and end-customer flow.

API-Led Payment Initiation And Environments

OneFin’s documentation describes a payment initiation API with separate sandbox and production endpoints. The request model includes:

• A merchant product code issued during merchant registration

• Currency and amount

• A unique merchant transaction reference

• A merchant callback URL to receive server-to-server results

• A response page URL for post-payment customer routing

• Parameters to select the payment method presented to the customer

The API design also incorporates message signing and verification expectations, which supports integrity controls across merchant-to-gateway communication.

Payment Methods Supported For Merchant Checkout

OneFin’s payment documentation and reference tables describe supported payment methods that can be offered on the OneFin gateway:

• Bank transfer via VietQR

• OneFin Wallet

• ATM cards via Napas

• International card schemes via Visa, Mastercard, and JCB

On the in-person side, OneFin also describes acceptance options that include contactless flows and mobile wallet payments in the context of POS-based experiences.

Payment Method Selection In The Gateway

Merchants can either let customers choose a method on the gateway or pre-select a method via API parameters. Documented method codes include:

• Visa, Mastercard, JCB (card acceptance)

• Napas ATM cards

• OneFin Wallet

• QR generation and VietQR scanning for transfers

QR Code Payments For In-Store And Digital Commerce

OneFin describes multiple QR-based acceptance patterns aimed at different merchant contexts:

• Static QR at the counter for offline stores where the customer scans a pre-displayed QR code to pay.

• Dynamic QR in a mobile app for online commerce flows, including merchants operating a website or an eCommerce storefront.

In practice, these approaches align to two common QR acceptance models:

• Merchant-presented QR (static at checkout)

• Transaction-specific QR (dynamic for an order or invoice context)

In-Person Acceptance: SmartPOS

OneFin’s SmartPOS solution is presented as an Android-based payment device that combines card reading and receipt printing in a single unit. SmartPOS supports multiple acceptance inputs, including:

• Chip cards

• Magnetic stripe cards

• Contactless cards (NFC)

• QR code payments

The SmartPOS materials also reference eKYC capture capabilities and broader integration potential with POS systems and management software used across sectors such as F&B, mini supermarkets, hotels, schools and education centers, and healthcare settings.

In-Person Acceptance: Tap To Phone (Contactless NFC)

OneFin also describes a “Tap to Phone” solution designed to let merchants accept contactless payments using a standard mobile device, without a traditional POS terminal. The described customer interaction is a tap-based flow where the customer brings a payment card into NFC range of the merchant phone, with the transaction processed through a OneFin-provided application.

This acceptance model is most relevant for:

• Mobile sellers and field commerce

• Pop-up retail and temporary locations

• Merchants that want to reduce reliance on dedicated POS hardware

Security And Compliance Posture For Merchant Use

OneFin describes PCI DSS certification and also outlines security measures and compliance-related controls in its privacy and data handling statements.

PCI DSS

OneFin states that it has been assessed and certified under PCI DSS, including references to a high security level. For merchants, PCI DSS alignment is typically relevant when evaluating a provider’s posture for card acceptance programs and operational controls.

Encryption, Secure Transport, And Integrity Controls

OneFin describes security measures such as:

• SSL for secure connections

• Encryption for data in transit and at rest

• Electronic signatures for transaction and information exchange

In its integration documentation, OneFin also describes signed messages and key exchange for API interactions, aligning with integrity and authentication controls for merchant-to-gateway communications.

AML And Risk-Related Compliance

OneFin also references compliance obligations related to anti-money laundering and counter-terrorist financing in the context of information sharing and legal compliance. While this is not a merchant pricing or underwriting disclosure, it indicates that OneFin frames its operations within regulated payment intermediary requirements and related compliance regimes.

Reporting, Reconciliation, And Transaction Operations

OneFin’s documentation includes operational elements that matter to merchant finance and support teams:

• Transaction status codes and state transitions (including an end-of-day batch settlement status concept in the platform’s status taxonomy)

• A status check API pattern, and an implementation note recommending merchants schedule a follow-up status query after a timeout window if connectivity is disrupted

• Callback and redirect mechanisms that help merchants reconcile customer-facing outcomes with back-office transaction states

Separately, OneFin’s merchant materials describe transaction management and operational optimization concepts, including automated reconciliation messaging for POS-oriented workflows.

Onboarding

OneFin’s merchant onboarding material describes a registration flow that includes:

• Submitting merchant information via a dedicated merchant portal URL

• A OneFin consultation and profile update stage

• Technical connection and acceptance testing

Merchant Fit: When OneFin VietNam Is Most Relevant

OneFin is most relevant for merchants that:

• Operate in Vietnam and want card + local transfer + QR coverage in a unified gateway experience

• Need QR counter payments for offline stores and a comparable flow for online orders

• Want hardware-based acceptance through SmartPOS, including receipt printing and multi-method acceptance

• Prefer phone-based contactless acceptance using Tap to Phone for mobile or event-based selling

It may also be relevant for organizations operating across multiple service environments, given the platform’s references to integration with POS systems and various types of management software.

Conclusion

OneFin VietNam provides a merchant payment acceptance stack that combines a redirect-based payment gateway, QR-led payment flows, and in-person acceptance options through SmartPOS and Tap to Phone. The documented method coverage includes VietQR transfers, OneFin Wallet, Napas ATM cards, and Visa, Mastercard, and JCB card acceptance, with additional references to mobile wallet payments in its POS positioning.