Bank of Ghana CISD 2026: SMS OTP before every transfer, lockout after 5 tries, and what the SMS can say
Robase · 2026-10-26
The Bank of Ghana's Cyber and Information Security Directive 2026 (CISD 2026) replaces the 2018 framework. In October 2026 the Governor said BoG will run thematic reviews of banks' compliance with it (GNA, 11 October 2026). GNA also reported in March that the new directive reaches beyond universal banks to savings and loans companies, microfinance institutions and fintechs (GNA, 27 March 2026).
Short answer. Yes, for the regulated institutions it covers. Paragraph 67(5)(c) says that before committing any money transfer order, the customer must enter an authentication code sent over a separate channel such as SMS or email, or use biometrics. Paragraph 73(2) says an SMS must not carry complete customer and account identification.
This page is education, not legal advice. Confirm scope and interpretation for your institution with your compliance lead. Robase is not a bank and is not licensed by BoG. Robase helps you build the SMS steps of a flow your compliance team signs off.
The transfer flow in five steps
- The customer submits a transfer with the receiver's details and the purpose of payment (67(5)(b)). Your app saves it as pending. Do not commit it yet.
- Send an OTP to the customer's registered phone with
POST /v1/otp/send. Robase generates the code and sends it. OTP goes out under Robase sender names after your first top-up, so you don't need your own Sender ID for OTP. - The customer types the code into your app. Call
POST /v1/otp/verifywithotp_idandcode. - Commit the transfer only after a successful verify. On a failure, add one to your own failed-attempt counter for that customer. At 5 in a row, block and require re-identification.
- After the commit, send a separate transfer alert with
POST /v1/sms/send. That is transactional SMS, and it goes out under your workspace's own approved Sender ID.
Steps 1 and 2: send the OTP
The request takes phone_number in E.164 format (for example +233...), an optional code_length from 4 to 8 (default 6) and an optional ttl_seconds up to 3600 (default 600). The response includes an id, which you store on the pending transfer and pass back as otp_id.
The OTP text is fixed for every country:
{code} is the OTP code for {app} app, expires in {minutes} mins.
{app} is the name of the API key's app. You can't add the amount, payee or any free text to the OTP message, so show those on your in-app confirmation screen instead.
Steps 3 and 4: verify, then commit
- A correct code returns 200 with
valid: true,status: "verified"andattempts_used. - A wrong code also returns 200, with
valid: false,attempts_usedandattempts_remaining. Checkvalid === true, never just the HTTP status. - Other errors return
{ "error": { "type", "message" } }. Match ontype: 400validation_error, 404otp_not_found, 409otp_expired(offer a resend), 409otp_already_verified, 409max_attempts_exceeded(count it as a failed attempt), 429rate_limited(honourRetry-After), 500internal_error.
Lockout after 5 failed attempts
Robase allows 5 attempts per OTP. After the fifth wrong code the API returns 409 max_attempts_exceeded. Verify calls are also limited to 10 per phone per workspace every 10 minutes.
A new OTP starts a fresh attempt count, so Robase's limit is not a customer lockout. The lockout belongs in your app: a counter tied to the customer, stored in your database, and not reset when a code is resent.
Paragraph 75(9)(c) caps failed login attempts at "no more than five consecutive attempts". Applying the same cap to OTP entry is our recommendation, not a quote from the directive. Paragraph 75(10) covers unblocking after re-identification.
Step 5: the transfer alert
POST /v1/sms/send takes phone_number, message and optional metadata. There is no sender field: Robase uses the workspace's default approved Sender ID, or its first approved one.
With no approved Sender ID the call returns 422 sender_id_required before any charge. Log it and alert your ops team. The transfer is already committed, so don't roll it back. You can request a Sender ID after one successful top-up, and approval usually takes 1 to 4 weeks. Track delivery with GET /v1/sms/{id} or the sms.sent, sms.delivered and sms.failed webhooks.
Code: Node
npm install @robasedev/sdk
import { Robase } from "@robasedev/sdk";
const robase = new Robase({ apiKey: process.env.ROBASE_API_KEY });
const MAX_FAILS = 5; // app-side customer lockout, applied from 75(9)(c)
export async function startTransfer(transfer) {
// transfer saved as PENDING by your app
const sent = await robase.otp.send({ phone_number: transfer.phone, code_length: 6, ttl_seconds: 600 });
await db.transfers.update(transfer.id, { otpId: sent.id });
}
export async function confirmTransfer(transferId, code) {
const t = await db.transfers.get(transferId);
if (await db.fails.count(t.customerId) >= MAX_FAILS) return { ok: false, reason: "locked" };
let result;
try {
result = await robase.otp.verify({ otp_id: t.otpId, code });
} catch (err) {
const type = err?.error?.type ?? err?.type;
if (type === "max_attempts_exceeded") return failAttempt(t);
if (type === "otp_expired") return { ok: false, reason: "expired_offer_resend" };
if (type === "rate_limited") return { ok: false, reason: "retry_later" };
throw err;
}
if (result.valid !== true) return failAttempt(t);
await db.fails.reset(t.customerId);
await commitTransfer(t); // only after verification
try {
await robase.sms.send({
phone_number: t.phone,
message: `Ref ${t.ref}: GHS ${t.amount} sent from acct ending ${t.last4}. Not you? Call ${SUPPORT}`
});
} catch (err) {
if ((err?.error?.type ?? err?.type) === "sender_id_required") alertOps("No approved Sender ID");
else throw err;
}
return { ok: true };
}
async function failAttempt(t) {
const n = await db.fails.increment(t.customerId);
return { ok: false, reason: n >= MAX_FAILS ? "locked" : "wrong_code" };
}
Code: Go
go get github.com/mantissatech/robase-sdk-go
client, err := robase.New(os.Getenv("ROBASE_API_KEY"))
sent, err := client.OTP.Send(ctx, robase.SendOTPParams{PhoneNumber: t.Phone})
// store sent.ID on the pending transfer
if fails(t.CustomerID) >= 5 { return ErrLocked } // app-side lockout
result, err := client.OTP.Verify(ctx, robase.VerifyOTPParams{OTPID: t.OTPID, Code: code})
if err != nil {
switch errorType(err) { // reads error.type from the API error body
case "max_attempts_exceeded":
return failAttempt(t)
case "otp_expired":
return ErrExpiredOfferResend
case "rate_limited":
return ErrRetryLater
default:
return err
}
}
if !result.Valid {
return failAttempt(t)
}
resetFails(t.CustomerID)
commitTransfer(t)
_, err = client.SMS.Send(ctx, robase.SendSMSParams{
PhoneNumber: t.Phone,
Message: fmt.Sprintf("Ref %s: GHS %s sent from acct ending %s. Not you? Call %s", t.Ref, t.Amount, t.Last4, support),
})
if err != nil && errorType(err) == "sender_id_required" {
alertOps("No approved Sender ID")
}
Code: PHP
composer require robase/sdk
$robase = new Robase\Client(getenv('ROBASE_API_KEY'));
$sent = $robase->otp->send($t->phone, 6, 600);
// store $sent->id on the pending transfer
if (failCount($t->customerId) >= 5) { return 'locked'; } // app-side lockout
try {
$result = $robase->otp->verify($t->otpId, $code);
} catch (Throwable $e) {
$type = errorType($e); // reads error.type from the API error body
if ($type === 'max_attempts_exceeded') { return failAttempt($t); }
if ($type === 'otp_expired') { return 'expired_offer_resend'; }
if ($type === 'rate_limited') { return 'retry_later'; }
throw $e;
}
if ($result->valid !== true) { return failAttempt($t); }
resetFails($t->customerId);
commitTransfer($t);
try {
$robase->sms->send(
phoneNumber: $t->phone,
message: "Ref {$t->ref}: GHS {$t->amount} sent from acct ending {$t->last4}. Not you? Call " . SUPPORT,
);
} catch (Throwable $e) {
if (errorType($e) === 'sender_id_required') { alertOps('No approved Sender ID'); } else { throw $e; }
}
errorType, failAttempt, alertOps, commitTransfer and the db calls are placeholders for your own app code, not SDK functions.
What the directive says, paragraph by paragraph
Source: BoG CISD 2026 (PDF).
| Para | What it says | What to build | | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- | | 67(5)(b) | A transfer order includes the receiver's details and the purpose of payment | Collect both before sending the OTP and show them on the confirm screen | | 67(5)(c) | Before "committing any money transfer order", the customer enters "an authentication code sent over a separate communication channel, such as short message service (SMS) or email", or uses biometrics | Hold the transfer as pending, send and verify an OTP, commit only on success | | 69(3) | Identification and authentication factors are delivered "securely and on separate channels" | Send the code by SMS to the registered phone, not inside the app session | | 69(4) | Services and transactions may depend on biometrics or a "one-time-password code delivered on a different channel" | Gate higher-risk actions, such as a new payee or a limit change, with an OTP step | | 70(8) | "Customer authentication method shall be based on multi-factor authentication" | Password or PIN plus SMS OTP, or biometrics | | 73(2) | SMS "shall not include complete identification details about the customer and the account, such as name, account number" | No full name and full account number in any SMS; mask the account to the last 4 digits | | 74(3), 74(4) | Alert customers immediately of unusual activity, through a different channel, with "only the minimal details required" | A short transfer alert through POST /v1/sms/send | | 75(9)(c) | Revoke access "after several failed login attempts ... no more than five consecutive attempts" | An app-side counter that locks at 5 and unlocks only after re-identification (75(10)) |
What an OTP SMS and a transfer alert may contain
- Never put the customer's full name and full account number in one SMS (73(2)). Safer still, use neither. A masked account and a reference number are enough.
- Keep alerts minimal (74(4)).
- Stick to plain letters, digits and basic punctuation. Write GHS rather than the cedi symbol, and avoid curly quotes and emoji, so each message stays in the 160-character GSM-7 encoding.
- The Robase OTP text, for example
482913 is the OTP code for Robase app, expires in 10 mins., carries no name or account number.
Example transfer alerts. You write these yourself, and they go out under your own approved Sender ID:
Ref TX48211: GHS 250.00 sent from acct ending 4417 on 20/10/26 09:14. Not you? Call 0302000000 now.Ref TX48211: transfer of GHS 250.00 declined. 5 wrong codes. Online access locked. Visit a branch or call 0302000000.New payee added to acct ending 4417. If this was not you, call 0302000000 now.
BoG's 7 October 2026 press release says no legitimate bank, mobile money operator, payment service provider or financial institution will ask for a customer's PIN, password or OTP by phone, text, email or social media. So an alert can end with We will never ask for your OTP or PIN.
What not to send: Kwame Mensah, acct 1234567890123 debited GHS 250.00. That puts a full name and a full account number in one SMS.
Who the directive covers
GNA reported that the new directive moves beyond universal banks to savings and loans companies, microfinance institutions and fintechs. The proportionality framework (PDF) groups institutions into tiers and sets how much of the directive applies to each. Check Annexure A with your compliance lead to see which paragraphs apply to your tier.
What BoG said in October 2026
At the Ghana Association of Banks AGM, Governor Asiama said BoG will run thematic reviews of compliance with the revised directive.
Cost and setup on Robase
SMS to Ghana costs 3 credits (NGN 18) per message as of 26 October 2026, from live pricing. One credit is NGN 6. New accounts start at 0 credits, and your first successful top-up adds bonus credits, once per account. OTP sends under Robase sender names right after your first top-up. Transfer alerts need your workspace's own approved Sender ID. Robase sends OTP and transactional SMS only, never marketing.
See SMS API for Ghana, the SMS OTP API, SMS OTP across Africa, what to check when an OTP SMS does not arrive, and the Nigeria angle on SIM swap checks with TIRMS.
FAQ
Does the CISD 2026 require an OTP before every transfer? Paragraph 67(5)(c) requires a code over a separate channel such as SMS or email, or biometrics, before any money transfer order is committed. Confirm how it applies to your tier with your compliance lead.
Can the SMS include the customer's name and account number? Paragraph 73(2) says SMS must not include complete identification details, such as name and account number. Mask the account and leave out the full name.
How many failed attempts before lockout? Paragraph 75(9)(c) caps failed login attempts at five in a row. You can apply the same cap to OTP entry. That is a design choice, not a quote.
Does the directive apply to fintechs and microfinance institutions? GNA reported in March 2026 that the new directive reaches savings and loans companies, microfinance institutions and fintechs. The proportionality framework sets the detail per tier.
Do I need a Sender ID to send OTPs in Ghana with Robase? No. OTP goes out under Robase sender names after your first top-up. Transfer alerts are transactional SMS and need your workspace's own approved Sender ID.
Start sending
Create a Robase account, top up, and send your first Ghana OTP from Node, Go or PHP. Your first successful top-up adds bonus credits, once per account.