| Scope of the product | One platform across seven bands — onboarding, acceptance, gateway, credit, ledger, risk, settlement. Seven modules ship today: KYC/KYB, POS, Marketplace, Payment Gateway, Fraud Detection, AML Monitoring, Reconciliation. Eight more are on the roadmap. | Acceptance and disbursement, plus gateway-side fraud screening. Onboarding orchestration, AML typology monitoring, and multi-source reconciliation are not its product. | Acceptance, disbursement, platform sub-accounts, and gateway fraud controls, across Indonesia and the Philippines. | Acceptance and disbursement with merchant tooling. | Acceptance and billing products, distributed through bank and enterprise channels. |
|---|
| Relationship to the rails | Not a licensed acquirer, and not trying to be. Payops is the layer above whatever rails you already use — including these vendors, whose settlement files it ingests. | It is the rail. You transact on its licence, at its published rates. | It is the rail. You transact on its licence, at its published rates. | It is the rail. You transact on its licence. | It is the rail. You transact on its licence. |
|---|
| Deployment model | SaaS or on-premise — a self-hosted, OJK-aligned platform that runs inside your own Kubernetes or Docker environment in Indonesia. | SaaS only. | SaaS only. | SaaS only. | SaaS only. |
|---|
| Compliance surface | AML monitoring on a configurable ruleset with goAML LTKM drafting and case management; KYC orchestration with document OCR for KTP, NPWP, and NIB plus in-house liveness scoring; and an immutable audit trail with statutory retention floors enforced by the platform — 10 years for financial records, 5 years for audit, compliance, and PII. | Fraud screening on its own traffic. Your PPATK reporting, KYC orchestration, and examiner-facing audit trail remain your project. | Fraud controls on its own traffic. AML typology coverage and case management are a separate purchase. | Risk controls on its own traffic; compliance tooling is separate. | Risk controls on its own traffic; compliance tooling is separate. |
|---|
| Reconciliation | A real engine: exact plus fuzzy matching (±Rp 500, ≤24h), exception classification with aging, per-merchant MDR deduction, maker-checker disbursement with CFO escalation above a per-tenant threshold, and per-source column-mapping profiles for any PSP, bank, or ERP extract. | Settlement reports for its own traffic. It cannot reconcile a competitor's rail or your internal ledger. | Settlement reports and a dashboard for its own traffic. | Settlement reports for its own traffic. | Settlement reports for its own traffic. |
|---|
| Pricing model | Per module, flat monthly on the managed plane; the whole platform on one contract at Rp 22.000.000/mo, or from Rp 180.000.000/yr on-premise. Directional — billing is not yet active. | Per transaction, permanently. There is no licence to own. | Per transaction, permanently. There is no licence to own. | Per transaction, permanently. | Per transaction, permanently. |
|---|
| Identity across the estate | Straventa Accounts — a self-hosted, multi-tenant OpenID Connect provider with single sign-on, step-up TOTP MFA, and descendant-scoped tenant permissions — is the same identity plane for every module and for your own applications, licensed per deployment rather than per seat. | Dashboard users and API keys scoped to its own product. | Dashboard users and API keys scoped to its own product. | Dashboard users and API keys scoped to its own product. | Dashboard users and API keys scoped to its own product. |
|---|
| Who builds and supports it | A Jakarta engineering team that also sells its time directly — hourly advisory, fixed-scope sprints, on-premise deployment work — so the people who wrote the module do the integration. | GoTo Financial merchant support and public documentation. | Vendor support tiered by account size, across multiple markets. | Vendor merchant support, Indonesian team. | Vendor merchant support, Indonesian team. |
|---|
| Honest limits | Eight of the fifteen modules — Recurring Billing, Issuing, Card Vault, Open Banking, Lending/BNPL, Ledger/Wallet, Disputes, Disbursement — are roadmap, not shipped. Billing is not switched on, so every price here is directional. And Straventa holds no payment licence of its own. | You cannot run it in your own environment, you cannot see or change its rules, and the per-transaction cost never stops. | You cannot run it in your own environment, and the risk rules are the vendor's, not yours. | You cannot run it in your own environment. | You cannot run it in your own environment. |
|---|
