You’ve decided to put wallets, payouts or cards inside your product. You’re evaluating infrastructure partners, and most of that evaluation is API coverage, rails and pricing. A different question will shape your team, your timeline and your cost more than any of those: what do you run once you’re live?
Running the programme is the day-to-day. Who reviews a flagged transfer at 2 AM? Who files covered and suspicious transaction reports with the AMLC? Who answers when the examiner asks? Who reconciles InstaPay, PESONet and QR Ph against your ledger every morning?
Most infrastructure gives you the API and leaves the rest to you: a KYC vendor, screening software, a disputes queue, a ledger, a reconciliation job, statements and regulatory reporting. That is a stack of vendors and policies before your first customer, and a team to run them.
TNKR is configurable. It can carry that operational load, or you can own it from day one. How much you take on, and when, is your decision.
Who owns what depends on the build you choose. Run it on your licence and your institution stays accountable to the regulator; TNKR runs the technology and the operations you delegate. Run it on ours and PayMongo is the licensed operator. The sections below describe the functions involved.
What you always own
Whichever build you choose, some obligations stay with you. You own the relationship with your customer, so you own the last mile.
| What it is | How TNKR helps |
|---|---|
Product and application security You build the product your customers use. Authentication, access control and securing your own application are yours. | TNKR stores and processes card and account data in PCI DSS Level 1 and SOC 2 Type 2 environments. More on that below. |
Marketing compliance Marketing a financial product under your brand carries disclosure and consumer-protection expectations. | TNKR can review how you describe the product before launch. |
Customer support Your customers will ask about their money. You run first-line support, with your own team or a provider. | The TNKR dashboard shows every account, transaction and state, so your support team answers without a ticket to engineering. |
What you can own or delegate
Everything below is what most teams expect to build, buy, staff and maintain. Without TNKR, each row is a separate vendor, integration and procedure. With TNKR, every row runs on one ledger that your team operates from.
| What it is | How TNKR helps |
|---|---|
Onboarding (KYC and KYB) Confirming a person or business is who they claim, before an account opens, against sources an auditor can check. | Create an account through the API. TNKR verifies its authorised representative, then activates it. |
AML monitoring and reporting Ongoing monitoring for money laundering, fraud and sanctions exposure, and the covered and suspicious transaction reports filed with the AMLC. | Screening and transaction monitoring run on TNKR’s compliance service. |
Disputes Intake, investigation and resolution when a customer says a transaction was unauthorised, wrong or never delivered. | Dispute workflows run on TNKR, with escalation handled by PayMongo operations. You don’t buy a case tool or train a disputes team. |
Reconciliation Matching every movement across InstaPay, PESONet, QR Ph, the e-wallets and the card network against your ledger. Invisible when it works. | Every movement posts to one double-entry ledger, with the rail’s reference on each transfer. |
Transaction decisioning Approve, decline, hold or route every movement against limits, velocity rules and risk signals, in real time. | Control evaluates each request against policies you write. Fraud rules can allow, block or send a payment for review. |
Ledger and statements A real-time record of every credit, debit and balance, and the statements and settlement reports that come out of it. | TNKR keeps the account-level ledger across wallets, payouts, cards and credit. Statements and settlement reports come from the same ledger. |
Card issuing and processing Issuing virtual and physical cards and authorising every transaction in real time, tied back to the account and ledger. | Virtual Mastercard prepaid cards under your brand, sharing a balance with the linked wallet. Physical cards are in development. |
Regulatory reporting The reports your regulator expects on programme activity and compliance performance. | On our licence, PayMongo reports as the licensed operator. On yours, TNKR exports the ledger and activity data your reports are built from. |
Sensitive data storage Storing card and account numbers in certified environments, with the audits and access controls that go with them. | TNKR stores card and account data in PCI DSS Level 1 and SOC 2 Type 2 environments. You get permissioned access through the API and dashboard; the data stays off your systems. |
Taking on more as you scale
TNKR carries every function above by default. Defaults are not constraints. Some teams have good reasons to own a function, at launch or years later.
Take onboarding review, transaction monitoring or disputes in-house as your team matures, and keep TNKR’s ledger, rails and tooling underneath. The split is written into your programme, function by function, and it changes when you do.
The point isn’t that you should own more. It’s that you can, on your timeline.
Get started
Read documentation — see how each function maps to endpoints, webhooks and controls.
Talk to an expert — work through the operating picture for your build.
Frequently asked questions
Originally published