The useful record in Vietdong is not a bank statement; it is the life cycle of a short-term unsecured loan. The app description names a phone-number registration flow, CMND/CCCD eligibility, a personal bank account requirement, quoted loan range, term, APR and repayment example. That is enough structured, server-side state to justify an API or protocol implementation for lenders, brokers, portfolio teams and support desks that need the status outside the phone screen.
We would build around the consented account session and the loan ledger shown to that user. No guessing. The integration is scoped to the fields that matter: application intake, approval result, disbursement event, repayment schedule and document evidence when the customer has agreed to that use.
The route we would use for Vietdong
For this app, the practical route is authorized interface integration and protocol analysis under the user's consent. Open Banking Studio maps the mobile flow, token or cookie chain, request signing if present, Vietnamese labels, error states and session renewal. The result is a controlled service that returns normalized loan records rather than screenshots or manual exports.
| Route | Reachable surface | Effort | Durability plan |
|---|---|---|---|
| Consented app-session capture | Logged-in borrower profile, application status, loan offer, disbursement and repayment views | Normal build route | Contract tests replay the real loan-status calls and alert on label or field changes |
| Document and screen evidence mapping | Identity checks, repayment example, loan terms and customer-service references visible to the user | Small extra layer | HTML and JSON parsers keep raw evidence hashes beside normalized fields |
| Manual export or support-led file intake | Any PDF, receipt, contract or account extract a consenting user can obtain during the engagement | Useful for first backfills | Importer reconciles imported rows against later app-session syncs |
The working build should start with the app-session path because Vietdong's valuable data changes as the loan moves from submitted to approved, paid out and settled. File intake is kept for old cases and dispute packs, not for the daily sync.
Loan fields an integrator can use
| Data domain | Origin in Vietdong | Granularity | Integrator use |
|---|---|---|---|
| Borrower identity profile | Registration and eligibility flow using phone number plus CMND/CCCD, age and Vietnam citizenship claims described by the app | Per consenting user | Match an applicant to CRM, servicing or compliance records without exposing more identity data than the project needs |
| Loan request | Requested amount and term, aligned to the listing's 1,000,000-50,000,000 VND and 91-365 day product description | Per application | Route approved, pending and declined cases into underwriting or lead-scoring workflows |
| Offer economics | APR, daily interest calculation and total repayment example as shown in the app description | Per loan offer | Check quoted cost against customer communications and portfolio reporting |
| Disbursement and bank-account link | The app says funds are paid after approval and that a personal bank account is required | Per approved loan | Reconcile payout status, settlement timing and customer-support tickets |
| Repayment schedule | Loan term, due dates, amount due and paid/overdue state once visible in the account | Per instalment or due event | Power reminders, hardship workflows, servicing dashboards and audit exports |
Source package for this lending flow
The handoff is source code and documentation a developer can run. For Vietdong that means a small Python or Node service, an OpenAPI file for loan-status queries, the auth-flow notes for the mobile session, fixtures for Vietnamese labels such as khoản vay and thời hạn, and automated tests that cover submitted, approved, disbursed and closed loan states.
We include retention guidance for identity evidence, consent-log schema, retry rules for expired sessions, and a field dictionary that preserves original labels beside normalized names. Short names matter here. VND values are returned as integers. Dates are stored with timezone notes when the app exposes only a local display string.
Example endpoint after protocol mapping
This is the kind of endpoint we expose after confirming Vietdong's real request fields during the build. It is not a claim about hidden routes; it is the contract our delivered service presents to your system.
GET /vietdong/accounts/{consent_id}/loans/current
Authorization: Bearer <client_token>
200 OK
{
"app": "Vietdong-Vay nhanh online",
"borrower_ref": "vdg_usr_8f21",
"currency": "VND",
"application": {
"requested_amount": 2000000,
"term_days": 120,
"state": "approved",
"submitted_with": ["phone", "cmnd_cccd", "bank_account"]
},
"pricing": {
"apr_percent": 18.25,
"daily_interest_percent": 0.05,
"total_interest": 120000,
"total_due": 2120000
},
"repayment": {
"next_due_date": "confirmed_during_build",
"status": "current"
}
}Vietnam consent and privacy handling
Vietnam's Government Portal lists Decree 13/2023/ND-CP on personal data protection, issued on 17 April 2023 and effective on 1 July 2023. Vietdong's own app description also says it follows that decree. For this integration, the consent record names the borrower, the data categories, the purpose, retention period and revocation path. Identity evidence is kept apart from ordinary sync logs.
Consumer lending adds another discipline: access is logged, audit trails are kept, and data is minimized to the receiving workflow. If a hosted endpoint is used, OpenBanking Studio stores the least possible payload and can sign an NDA where the data processor terms require it.
Engineering points that matter for Vietdong
Vietnamese loan apps often mix product copy, account status and customer-service notices in the same mobile views. We map the display strings to stable fields, then keep the original Vietnamese text in evidence so a support agent can see exactly what the borrower saw.
The app's product description uses both annual APR and a daily interest example. We model both. That prevents a downstream dashboard from comparing a daily figure against an annual figure and flagging a false mismatch.
Vietdong eligibility depends on CMND/CCCD, age, citizenship and a personal bank account as described in the listing. The build treats those as consent-scoped fields. Access, test accounts and approvals are coordinated during the project, while the client only needs to tell us which records and outputs they want.
Interface evidence kept with the build
Screenshots are useful for field naming and regression checks. We keep them as evidence while the automated tests validate the live protocol behavior.
Checked sources for this mapping
Reviewed by the OpenBanking Studio integration desk on 2026-07-10. We checked the Google Play record for Vietdong-Vay nhanh online, Vietnam's Government Portal page for Decree 13/2023/ND-CP, and current Vietnam online-lending comparison pages from Home Credit Vietnam and Techcombank. The point was to anchor the data domains, not to rate the loan product.
Other Vietnam lending apps often mapped nearby
Home Credit holds application, limit, repayment and customer-service records for consumer loans.
FE ONLINE 2.0 connects cash-loan and card application flows to FE CREDIT servicing data.
VPBank NEO includes bank-account and loan-product surfaces that may be normalized alongside Vietdong for a borrower view.
Cake by VPBank brings digital-bank onboarding, loan offers and repayment states into the same consumer-credit category.
Techcombank Mobile is relevant where a portfolio wants bank-backed loan and overdraft records in one schema.
VCB Digibank adds Vietcombank account and credit-product status for users who compare bank and non-bank borrowing.
MoMo Vay Nhanh links wallet identity, partner eligibility and loan offers.
ZaloPay and Viettel Money are wallet-led routes where repayment reminders and eligibility events can sit beside lending records.
Questions Vietdong integrators usually ask
Can the build track a Vietdong loan from application to repayment?
Yes. The useful model is an application ledger: submitted profile, requested amount, term, quoted cost, approval state, disbursement event, repayment schedule and closure state, all captured only for consented accounts.
How does Vietnam's data-protection decree affect this work?
The integration keeps a record of the user's consent, stores only fields needed for the agreed use case, and separates sensitive identity material such as CMND or CCCD evidence from ordinary sync logs. Decree 13/2023/ND-CP is the named Vietnam personal-data instrument cited for the build.
Will the integration handle Vietnamese-language screens and currency fields?
Yes. Field mapping keeps Vietnamese labels such as khoản vay, thời hạn and lãi suất beside normalized names, while monetary values are returned as VND integers so downstream accounting systems do not parse formatted text.
Where is the stable handoff point for a lender or aggregator using Vietdong records?
The handoff is a small service with tested endpoints for loan status, borrower profile fields, repayment schedule and document evidence. It can run inside the client's environment or behind OpenBanking Studio's hosted endpoint.
Collapsed app profile
Vietdong-Vay nhanh online facts used here
Vietdong-Vay nhanh online is described as a Vietnam unsecured online-loan app. The supplied app description names phone-number registration, a 5-10 minute application process, no collateral or guarantor, disbursement after approval, loan amounts from 1,000,000 to 50,000,000 VND, terms of 91-365 days, a maximum APR of 18.25% per year, CMND/CCCD eligibility, age 18 or older, Vietnam citizenship and a personal bank account. It lists the website tinvietetsco.com.vn, privacy-policy URL, support email, hotline and Hanoi address.
For a Vietdong project, OpenBanking Studio can deliver source-code delivery from $300 — runnable API or protocol-implementation source plus docs, paid after delivery once you are satisfied — or a pay-per-call hosted API with no upfront fee; the usual build cycle is 1-2 weeks, and the next step is to send the app name and required fields through the contact page.