Payment preprocessing
with controlled execution
Regence AI supports evaluation of domestic and cross-border payment preparation: retrieve context, execute evidence checks, review policy requirements and obtain a test quote before human review.
Official Mojaloop Testing Toolkit peer. This environment simulates a financial service provider. It is not a full Mojaloop hub, a connected bank, a clearing service or a real-money payment rail. Cross-border scenarios use XTS test units without FX conversion.
Evaluation workflow
- Payment context: retrieve fictional payer, beneficiary and payment records through the Finacle integration simulator.
- Preprocessing controls: check identity evidence, synthetic screening status, purpose, configured test limits and corridor.
- Policy retrieval: retrieve versioned illustrative control profiles and identify requirements that need institutional validation.
- Test quote: submit an FSPIOP quote request to the toolkit and correlate the asynchronous callback.
- Human review: accept, return or escalate the advisory brief. Failed controls block execution.
- Explicit test execution: an accepted, eligible review can submit a separate test transfer and record the peer callback. No real funds move.
API interaction
Download the Regence evaluation API specification ↗
| Interface | Operation | Purpose |
|---|---|---|
| Regence application | POST /api/cases | Start credit or payment agent evaluation |
| Regence application | GET /api/cases/{id} | Review evidence and actual execution trace |
| Regence application | POST /api/cases/{id}/review | Record human disposition |
| Regence application | POST /api/cases/{id}/test-transfer | Explicit, eligible test transfer after review |
| Internal Mojaloop test peer | POST /quotes → PUT /quotes/{id} | Asynchronous test quote exchange |
| Internal Mojaloop test peer | POST /transfers → PUT /transfers/{id} | Asynchronous peer transfer outcome |
Application API calls require evaluation login and same-origin requests. Toolkit administration and database ports are internal. The WebUI includes an API inquiry console and exportable case trace.
Domestic and cross-border scenarios
Domestic samples represent a Nigeria-to-Nigeria jurisdiction scenario. Cross-border samples represent Nigeria-to-Ghana, using the same XTS test currency. A separate exception scenario demonstrates unresolved beneficiary identity and screening evidence; it must remain on hold.
Regulatory and institutional controls
Evaluation checks are illustrative and do not certify compliance. Before bank deployment, legal and compliance stakeholders must validate applicable rules, effective dates, licensing, FX eligibility, reporting obligations, sanctions sources and delegated authority for each corridor. The model cannot override deterministic holds.
Reference material: CBN AML/CFT supervision and CBN payments system supervision. These references identify regulatory context; they are not a complete approved control mapping.
External sandbox integration
Connection to an external Mojaloop hub requires authorised participant credentials, supported API versions, callback registration, JWS and TLS configuration, scheme rules and test participants. The current toolkit peer does not validate a full hub integration, ILP security, net debit caps or settlement.
FLEXCUBE uses an implemented synthetic inquiry connector. Finacle integration data is simulated; no vendor sandbox is connected. The application does not provide an Oracle, Finacle or Mojaloop certification.