WHAT IT IS
AcceptCore is INM's merchant payment-acceptance platform. It gives merchants multiple ways to get paid - QR code, payment requests to a phone number, embeddable payment buttons for their own website (with PHP and JavaScript integration examples), and SoftPOS / Tap-to-Phone acceptance on certified Android devices - behind one merchant portal for transactions, sales, users, acceptance points and API keys. A companion bank-side console onboards, configures and supports every merchant and acceptance point. None of this asks the bank to rearrange its plumbing. The core in production and the market's own payment network are both reached through adapters, and no particular processor or switch is taken for granted.
THE PLATFORM
Total sales and refunds for the selected period, transaction counts and the daily curve, with comparison against the previous period.
The merchant generates a QR code for the amount due, shares it as a link and guides the customer through the five payment steps in the bank's app.
Every counter or terminal with its account, phone number, default flag and status - searchable, filterable and ready to add a new point.
WHY IT MATTERS
Merchants get paid however their customers want to pay - in person, by phone, by QR code, or through their own website - while the bank runs one console to onboard, configure and support every merchant and every acceptance point. Which core the bank runs, and which network the market settles on, are adapter questions - neither is baked in.
FEATURES
QR code, phone-number payment requests and embeddable web payment buttons - three ways to request a payment without a physical terminal.
SoftPOS / Tap-to-Phone acceptance on certified Android devices for face-to-face payments.
Transaction management: search, multi-field filters, full or partial refunds with SMS validation, PDF receipts and Excel export.
Sales summaries aggregated by period and transaction type.
Multi-point acceptance management - create, activate/deactivate and set a default acceptance point, each with its own QR code and callback address.
Role-based merchant users (Admin, Supervisor, Technical Administrator, Customer Assistant) with per-channel notification preferences (push, email, SMS).
Security-key and API-key issuance, with documented SOAP/REST endpoints for point-of-sale and merchant-management integrations.
Bank-side console to onboard a merchant end-to-end - data, acceptance points, admin user, summary, batch QR generation - and to activate, suspend or reconfigure any merchant.
ADVANTAGES
QR code, phone-number payment requests, embeddable web payment buttons and tap-to-phone acceptance are all managed from the same merchant portal - no separate systems to reconcile.
Merchants manage their own users, acceptance points, notifications and API keys day to day; the bank keeps onboarding, activation and configuration.
Payment buttons ship with ready PHP and JavaScript examples, so a merchant's own website can start accepting payments without a bespoke integration project.
One merchant account manages many acceptance points, each with its own users, permissions, notifications and default settings.
One platform behind every acceptance channel a merchant uses - from a face-to-face tap to an embedded payment button on their own website.
BUILT FOR
One console to onboard, configure and support every merchant and every acceptance point.
Payment buttons for the website, QR code or phone-number requests for remote sales, tap-to-phone for face-to-face.
QR code and phone-number payment requests need nothing beyond a smartphone.
Security keys, API keys and documented SOAP/REST endpoints for in-house point-of-sale software.
HOW IT WORKS
The bank registers the merchant, its first acceptance point and an admin user in one guided flow.
The merchant requests payment by QR code, phone number, an embedded payment button, or a tap on a certified phone.
The customer completes the payment; refunds, full or partial, are validated by SMS.
The merchant tracks transactions and sales, manages users and acceptance points, and integrates further via security and API keys.
It's INM's merchant payment-acceptance platform. It gives merchants multiple ways to get paid - QR code, phone-number requests, embeddable payment buttons and tap-to-phone - behind one merchant portal and one bank-side console to onboard and manage them.
Yes. The core connection is adapter-based - Banka, Finastra Essence, an in-house legacy system, whatever is already there - over API/ISO, with no change to the central system. The domestic side works the same way: each market's clearing house, EMIS in Angola included, plugs in through an adapter.
Both. Banks in markets with data-residency requirements usually choose on-premise; SaaS where regulation allows it.
No. Tap-to-Phone is one of several acceptance channels. Merchants can also accept payments by QR code, phone-number payment requests, or an embeddable payment button on their own website - all managed from the same portal.
INM's own teams - we don't subcontract implementation. The same team runs, evolves and supports the product 24/7 after go-live.
Talk to our team to see how this product fits your ecosystem.