Phone (021) 5431 4531  ·  info@spesolution.com — SPE’s only official contacts Received a suspicious offer in SPE’s name? Report it here

Solutions

Banks & Financial InstitutionsVirtual account & QRIS acquiring under your bank’s brandEnterprise & Digital BusinessIncoming payments identified and reconciled automaticallyService BusinessesBooking, payments, and customers in one app

Products

SPECVAVirtual Account Management SystemQRISANQRIS Acquiring Management SystemCRING!Payment facilitator for enterprise & governmentCRING! PointBooking & customer management for service businesses

Portfolio

Case StudiesTrack record per client: BNI, Permata, Bank JakartaProjects11 QRIS and virtual account implementationsPress ReleaseThree press releases and 32 media coverage linksTrust CenterLicences, certifications, and complianceBlogCompanyCareersTalk to our team
SPECVA logo
Virtual Account Management System · for banks

Operations teams stop spending their mornings matching bank statements.

Every VA payment is validated on arrival, matched automatically against core banking statements, and closes the invoice in your corporate customer's system — under your bank's own brand.

The engine behind bank VA services since 2016 · in PCI DSS & ISO/IEC 27001:2022 scope · SPE holds a PJP Category 3 licence from Bank Indonesia

Manual reconciliation from account statements every morning
Payments matched automatically; the team only handles exceptions already labelled with a reason
Callbacks fail silently; corporate customers call before you know
Signed callbacks with queuing & automatic retry — failures show on the dashboard and can be resent
Settlement and regulator reports rebuilt every period
Per-business-unit reports and Bank Indonesia templates generated automatically from the same data
Who it's for

Built for the teams that carry the bank's collection services

SPECVA is a white-label product: the bank stands out front, SPE supports from behind.

Transaction Banking

Head of Transaction / Cash Management

Offer VA Credit & Collection services to corporate customers — schools, insurers, regional governments, platforms — without building a VA engine from scratch.

Digital Banking

Head of Digital Banking / Product Owner

Add VA issuance, billing, and top-ups to the bank's digital channels with numbering schemes and rules controlled by product.

Technology

CIO / CTO & the bank's IT team

Need a system that connects cleanly to core banking, keeps a complete audit trail, and runs within the bank's infrastructure controls.

The problem today

Issuing a VA number is easy. What's expensive is what happens after it's paid.

VAs carry the high-value invoices: tuition fees, insurance premiums, regional taxes, top-ups, instalments. Without a management system, the burden shifts to the operations team.

  • Account statements matched against invoices by hand — every day, for every business unit.
  • Expired VA numbers left open; duplicate payments and wrong amounts slip through unflagged.
  • Callbacks to the customer's billing system fail with no retry — invoices stay open even though they've been paid.
  • Reports for finance and the regulator rebuilt manually every period.
How it works

Five steps, from issuance to reporting — with no manual touch

Billing system / ERPinstitutions · universities · insurersregional govt · digital platformsSPECVAVA Management Systemruns on the bank's infrastructureunder the bank's brandCustomer paysmobile banking · ATM · tellerinterbank transferCore bankingbank account statementsAutomatic reportssettlement · finance teamBank Indonesia templatesIssue VA — API / dashboardIssue VA — API / dashboard1Inquiry & paymentInquiry & payment2Validation & responseValidation & response3Signed callback + automatic retrySigned callback + automatic retry4Automatic reconciliationAutomatic reconciliation5ReportingReporting

The SPECVA flow: a VA is issued from the billing system, paid by the customer through the bank's channels, validated, sent as a callback, reconciled against core banking, and reported automatically.

  1. IssueThe institution's billing system calls the SPECVA API (or dashboard) to create a VA — amount, validity period, invoice reference.
  2. PayThe customer pays the VA number via mobile banking, ATM, teller, or interbank transfer; the bank forwards inquiry and payment to SPECVA.
  3. ValidateSPECVA checks the amount, validity period, and invoice status, then responds to the bank's channel.
  4. CallbackThe institution's system receives a signed notification; on failure, SPECVA retries automatically and logs it on the dashboard.
  5. Reconcile & reportEvery payment is matched against core banking statements; settlement reports and regulator templates are generated automatically.
Capabilities

What SPECVA manages

Virtual Account issuance

  • Static VAs — one fixed number per customer for top-ups and recurring payments.
  • Dynamic VAs — a number per invoice, with locked (closed) or open amounts, validity periods, minimum/maximum limits.
  • Bulk generation — mass issuance via file or API for periodic invoices (tuition, dues, premiums).
  • Prefixes & numbering schemes per business unit — collections separated by branch or by programme.

Notifications & callbacks

  • Real-time HTTP callbacks to the billing system/ERP with signatures and idempotency keys.
  • Queuing & automatic retry on an exponential schedule; failed callbacks appear on the dashboard with a resend button.
  • Customer notifications through the bank's channels (SMS, email, push) as configured.

Reconciliation & settlement

  • Automatic matching against core banking statements; exceptions flagged with a reason — amount mismatch, expired VA, duplicate payment.
  • Settlement reports per business unit and per period, exported to finance-team and regulator formats.
  • A complete audit trail: who issued, when it was paid, where the callback went, when it was reconciled.

Dashboard & control

  • Operations dashboard: active VAs, today's payments, match rate, pending callbacks.
  • Maker–checker for sensitive operations — bulk VA closures, callback URL changes.
  • Bank Indonesia report templates and the bank's internal reports.
Integration

It joins the bank's systems — it doesn't replace them

Adaptors to core banking, REST APIs to institutional customers' systems — all under the bank's control and brand. High Availability data centers at Lintasarta, DCI Indonesia, and Google Cloud.

  • Core banking adaptors — mapping inquiry, payment, and statements for reconciliation.
  • REST API + sandbox — documentation and callback examples for the institution's developer team.
  • Full channel coverage — mobile banking, ATM, teller, and interbank transfers flow into one validation engine.
  • Security — encryption in transit and at rest, role-based access control, audit logging.
Illustration
// Creating a dynamic VA — illustrative example, not a final specification
POST /va/v1/virtual-accounts
{
  "customer_name": "Universitas Nusantara",
  "amount": 7500000,
  "amount_type": "closed",
  "expired_at": "2026-10-01T23:59:59+07:00",
  "bill_reference": "SPP-2026-09-0812",
  "callback_url": "https://billing.institusi.ac.id/hooks/va"
}

// Callback when a payment arrives
{
  "va_number": "988801000123456",
  "status": "PAID",
  "paid_at": "2026-09-08T09:12:44+07:00",
  "signature": "a91f…"
}
Portfolio

Nine years as the VA engine behind banks

SPECVA is the new name (2024) for the same VA platform — built, tested, and grown in bank production environments since 2016.

BNI eCollectionBNI Autodebet BNI Digital InvoiceAutoPay SmartPay by BNI DIGI BankingPJP Category 3 — BI

See the case studies →  ·  Trust Center →

2016
The VA Credit application for BNIThe start of the platform now called SPECVA.
2018
PCI DSS certificationThe payment industry's data security standard.
2019
VA Credit, a digital wallet & YAP! with BNIThe platform expands into BNI's payment ecosystem.
2022
The VA Credit system with Bank DKILaunched in 2023 alongside Bank DKI's QRIS and Debit.
2024
Rebranded as SPECVA · PJP Category 3 licenceThe core VA becomes an official product; SPE is licensed by Bank Indonesia.
Next step

From mapping to go-live, with the same team beside you

Step 1

Assessment

Mapping channels, core banking, numbering schemes, and reporting needs with your team.

Step 2

Integration & configuration

Core banking adaptors, callbacks to institutional systems, reconciliation and numbering rules.

Step 3

Phased go-live

Testing with pilot institutional customers, then expansion — with monitoring and help desk.

Discuss your bank's VA scheme

Tell us which channels and core banking you use — our team maps the architecture and implementation steps with you.