Bank onboarding

Signed participation agreement (MerasPay clearing terms), AML/CFT attestation aligned with BCD circulars, fee schedule acknowledgment, two named operational contacts + an incident-response runbook.

Your BIC (11 chars, e.g. BSABDJJDXXX), your settlement BIC (where DJF sweep wires arrive — typically your BCD account), per-transaction max + daily cap, and your approval threshold (default 5,000,000 DJF).

Provision two keys; MerasPay holds the public halves. mTLS client certificate — your servers present this when calling api.merashub.com/banking/v1/*. We pin against the sha256. JWS signing keypair (RSA-2048 or EC P-256) — your servers sign every request body, we verify with the public half. Upload public PEMs via the admin portal or send to your MerasPay onboarding contact.

MerasPay provisions a sandbox credential. Your team runs the conformance suite — a fixed sequence of pacs.008 scenarios designed to exercise the happy path and every documented failure code. You pass when every scenario produces the expected pacs.002. Scenarios include: happy path settle, insufficient funds (AM04), bad creditor account (AC01), duplicate UETR, large amount (ACWP), sanctioned-name hit (ACWP), post-settlement return.

Once conformance passes, you open MerasPay's nostro account at your institution with the configured target balance. We configure min / target / max bands; the liquidity manager watches.

MerasPay's admin team submits a 4-eyes approval request to flip your bank from pending to active. Once approved, your sandbox credential is duplicated into production and you can start sending live pacs.008.

From day one you receive camt.054 credit/debit notifications in real time (or near it) and a daily camt.053 statement at 23:59 UTC. Your core system reconciles MerasPay's vostro (your view) against your own records overnight.