Integration is where banks lose time and money. Configured, not coded.
Every channel, network and partner your bank connects is usually built by hand, and each one carries its own risk. The ESB Platform replaces that hand-wiring: your own team adds channels, partners and rules by configuration, and every change is tested and approved before it goes live.
New channels take months
Every new ISO 8583 variant, partner API or wallet becomes a development project, with vendor change requests and long test cycles.
Timeouts turn into disputes
When a backend does not answer, payments end in doubt: customers charged twice or money stuck, settled later by hand.
Every change is a risk
One change to a shared integration can break another channel, and nobody can see the impact before it goes live.
Compliance weighs on everything
Card data, audit trails, four-eyes approval and scheme mandates add work to every integration.
Connect a new partner in days.
Each partner API was a development project.
The AI assistant reads the partner's specification and proposes the field mapping, tests and error codes. An analyst reviews the one field it was unsure about, runs the tests and submits for approval.
Nothing is applied without a person's approval.
New partner: wallet top-up API
REST partner to core banking (ISO 8583) · draft change set CS-1047 · imported from the partner's OpenAPI specification
| Partner request (JSON) | Operation | Core banking (ISO 8583) | Status |
|---|---|---|---|
| merchantRef string | copy | F37 Retrieval ref an12 | AI · verified |
| customer.walletId string | lookup: wallet → account | F102 Account ans..28 | AI · verified |
| amount.value decimal | to minor units · pad 12 | F4 Amount n12 | AI · verified |
| amount.currency string | ISO 4217 → numeric | F49 Currency n3 | AI · verified |
| txnTime datetime | format MMDDhhmmss | F7 Date/time n10 | AI · verified |
| channel string | lookup: channel → MCC | F18 Merchant type n4 | Review |
| narration string | truncate 40 | F43 Narrative ans40 | AI · verified |
| Sample message | Expected | Result | Time |
|---|---|---|---|
| Top-up PKR 2,500 | 00 Approved | Pass | 41 ms |
| Top-up above wallet limit | 61 Exceeds limit | Pass | 38 ms |
| Duplicate request (same merchantRef) | Original answer returned | Pass | 6 ms |
I read the partner's OpenAPI file and your existing wallet integrations, and proposed the mapping, 12 test cases and the error-code table.
Needs your review: the partner sends a channel code with no exact match in your MCC table. I suggested 6540, based on the other wallets. Please confirm.
- Every field cites the spec line it came from
- Amount conversion tested on 6 samples
- Duplicate protection on merchantRef
- Response codes mapped to the channel
Proposals are never applied without a person's approval.
Reconciliation that mostly does itself.
Settlement breaks were worked by hand, line by line.
Settlement files are matched automatically; AI proposes fixes for the rest, citing the exact settlement lines.
Proposals apply only within limits the bank approves; the rest go to an officer.
Reconciliation · 12 Oct 2026
1LINK, Raast, scheme and core banking settlement files · last file received 06:10
| Payment | Amount | Problem | AI proposal and the evidence it cites | Proposed action | |
|---|---|---|---|---|---|
| 1LINK · IBFT out | PKR 12,500 | Unresolved after timeout | Posted at 1LINK: settlement line 4,218 (STAN 004123, same amount, same account)✓ Evidence checked against source files | Mark completed | Review |
| ATM · withdrawal | PKR 20,000 | Core posted, ATM reversed | Reversal advice line 911 matches; core debit still open✓ Evidence checked against source files | Reverse core debit | Review |
| Raast · inbound credit | PKR 3,000 | Credit not found in core | Raast settlement line 77; no core journal; credit pending✓ Evidence checked against source files | Credit customer | Review |
| POS · purchase | PKR 8,450 | Amount mismatch | Scheme file shows PKR 8,540 (digits swapped at terminal)✓ Evidence checked against source files | Officer review | Review |
Compliance built in.
Card data protected end to end, a second pair of eyes on every change, and a complete record of who changed what and when. Designed so your auditors spend less time asking and more time confirming.
CS-1047 · Wallet top-up API
Submitted by Sana K. (maker) at 14:32 · you are the checker
| Item | Detail | Change |
|---|---|---|
| Service definition | wallet-topup | New |
| Field mapping | 7 fields, partner → ISO 8583 | New |
| Route | Wallet top-up → core banking | New |
| Response codes | 12 partner codes mapped | New |
| Partner quota | 50 requests/s, burst 100 | New |
- 14:02Sana K. created change set CS-1047
- 14:05AI assistant proposed mapping and 12 tests
- 14:11Sana K. confirmed F18 merchant type 6540
- 14:29Test run 12 of 12 passed on UAT
- 14:32Sana K. submitted for approval
Card data protected end to end
Designed for PCI Secure Software validation.
Four-eyes on every change
A second person approves; makers cannot approve their own work.
Tamper protection
Approved configuration is signed; altered configuration never runs.
Complete audit trail
Every change, approval and investigation recorded.
Bank sign-in and SIEM
Staff sign in through the bank; security events go to the SIEM.
Keys your way
HSM for PIN and MAC; no mandatory HSM for everything else.
See it on your own channels and backends.
Book a demo and we'll walk through the Integration Studio, a live transaction trace and reconciliation on the rails you run today. Or join the pilot programme and shape the platform with us.
Thanks, we've got it.
An AiMarks solutions lead will reach out within one business day to schedule your session.