Safehaven MFB

Named NGN accounts at Safehaven, inward transfers and daily statements.

Connect Safehaven MFB to bind its NGN account numbers to your wallets, credit what arrives in them, and reconcile each day against Safehaven’s own records.

Connector id	safehaven
Kind	BANK
Status	Available
Modes	Ledger-only or full integration
Currencies	NGN
Bank code	090286
Settlement account	AST:SET:NGN:SHV
Suspense account	LIA:SUS:NGN:SHV

​

Capabilities

Capability	Status
Named NGN accounts, opened by you and bound to wallets	Available
Inbound credits, confirmed with Safehaven	Available
Daily statements and reconciliation	Available
Name enquiry	Planned, with payment orders
Payouts through payment orders	Planned, with payment orders
Currencies other than NGN	Not supported

​

Before you connect

• A signed agreement with Safehaven MFB, and a corporate account.
• An OAuth app on the Safehaven dashboard, for full integration.
• An NGN ledger, with the settlement and suspense accounts above.

​

Credentials

Full integration, and read-only history access, ask for these. See Connecting a bank for where to enter them.

Field	Where to find it
environment	sandbox or production.
client_id	The OAuth client ID of the app you registered on the Safehaven dashboard.
company_url	The URL you registered the app with.
private_key	The app’s RSA private key, in PEM form. Paste it with its BEGIN and END lines.
main_account_id	The _id of your main Safehaven account. This is not its account number.

When you save them, PanoQore signs in to Safehaven and reads your main account. The console shows the account name Safehaven reports, so you can see you connected the right one.

​

Accounts

You open each account with Safehaven, as a sub-account under your app, using the customer’s BVN or NIN. PanoQore holds no personal data. Then you bind the number to a wallet.

In full integration, PanoQore first finds the number among your sub-accounts, checks it is active, and uses Safehaven’s name for it. A number that is not one of yours cannot be bound.

​

Inbound credits

In full integration, Safehaven posts notices to your webhook URL. PanoQore reads two kinds:

Notice	What it is
virtualAccount.transfer	A transfer into a virtual account.
account.credit	An inward transfer to your main account or a sub-account.

Anything else, debits included, is not a credit and is ignored.

Safehaven does not sign its notices, so a notice is never trusted. PanoQore asks Safehaven for the transfer by its session id, and credits only a transfer Safehaven reports as completed, inward and not reversed, for the amount Safehaven states. A notice Safehaven does not confirm posts nothing. If Safehaven cannot be reached, the notice is refused and Safehaven sends it again.

Each hour, PanoQore also pulls completed inward transfers to your main account and every bound sub-account, and posts any a notice missed. The transaction id is Safehaven’s session id, or its payment reference where there is no session id, so the same transfer never posts twice.

In ledger-only mode, report each credit yourself with POST /v1/partners/safehaven/credits. See Record a credit.

​

Statements

Safehaven has no statement to download. Where PanoQore can read your history, it builds each day’s statement from the completed transfers, in and out, on your main account and bound sub-accounts, and matches it each morning. Reversed transfers are left out, because the money did not move.

Otherwise, upload the day’s statement. See Reconciliation.

​

Amounts

Safehaven writes amounts in naira. PanoQore converts them to kobo, and refuses an amount that is not a whole number of kobo rather than round it.

​

Limitations

• NGN only.
• PanoQore does not open accounts at Safehaven. You open them and bind them.
• Payouts and name enquiry are not available yet.