CAC Payment Pending — How to Clear the Stuck State

The CAC dashboard reads Pending but the bank already debited the account. That single symptom hides four structurally distinct payment states between the bank, Remita, and CAC's reconciliation queue. The recovery sequence is different for each. Naming the state first is what stops a panicked re-payment that creates a double debit.

The single most useful action across all four states is to read the Remita status before doing anything else. Every recovery sequence below starts with that read, because the dashboard's Pending state alone does not tell you which leg of the route is holding the payment.

A CAC payment passes through three institutions, and the diagnostic depends on knowing which one is responsible for which piece of information.

For payment specifically:

• The bank holds the truth about whether your account was actually debited. The debit alert, the bank statement, and the bank's customer-care log are the canonical sources. The bank cannot tell you whether CAC has reconciled the payment; it can only tell you that the funds left your account.
• Remita holds the truth about whether the payment routed through the inter-bank settlement cycle and reached CAC's reconciliation endpoint. The RRR status at remita.net is the canonical source. Remita cannot tell you whether the CAC application has cleared into Paid; it can only tell you whether its leg of the route succeeded.
• CAC holds the truth about whether the iCRP dashboard has flipped the application from Pending to Paid and is now processing the registration. The iCRP portal status against the application reference is the canonical source. CAC cannot tell you why a payment failed at Remita; it can only tell you what its reconciliation queue currently reads against your application.

The diagnostic sequence below walks each of those three sources in order. Reading them out of order — chasing CAC for an answer that only the bank holds, or chasing the bank for an answer that only Remita holds — is the most common source of compounded confusion.

1. 1
   Confirm the bank actually debited the accountCheck the bank's SMS or email alert from the time of the payment attempt. If no debit landed, you are in State 4 — the payment never started, and you can safely pay again against the same RRR (within the validity window) or generate a fresh one. Skip to the State 4 recovery below.
2. 2
   Find the RRROpen the application on icrp.cac.gov.ng. The Remita Retrieval Reference is on the payment-summary view of the application; it is also in the bank's payment-confirmation message and on any receipt printed at the bank counter. Save the 12-digit RRR — every subsequent step references it.
3. 3
   Read the RRR's status at RemitaGo to remita.net, select 'Check the status of your payment' (or the equivalent verify-RRR option), and enter the RRR. The response will read Successful, Pending, Failed, or Not Found. That state determines which recovery flow below applies. Do not skip this step; the iCRP dashboard's Pending state alone is not a diagnostic.
4. 4
   Cross-reference the iCRP dashboardLog into icrp.cac.gov.ng and open the application. The dashboard's status sits next to the application reference. Note whether it reads Pending, Paid, Submitted, Queried, or Approved. Pair the iCRP status with the Remita status to identify which of the four states applies.
5. 5
   Wait the reconciliation window before any actionFor card payments on the portal, wait at least one hour from the time of the bank debit. For bank-counter payments via the RRR, wait at least 24 hours; allow the full 48 hours before treating the state as truly stuck. Most cases self-resolve within these windows.

Once you have read the three states — bank debit, Remita RRR status, iCRP dashboard — you can identify which of the four payment states above applies. The recovery for each is below.

This is the routine wait. Remita has done its part; CAC's reconciliation queue has not yet completed.

• Card payment within the last hour. Wait. The reconciliation typically clears within the hour for card payments. Refresh the iCRP dashboard once or twice; do not re-pay.
• Bank-counter payment within the last 24 hours. Wait. Bank-counter payments take longer to settle because they pass through the bank's clearing cycle before Remita confirms to CAC. The full 48-hour window applies before treating the state as stuck.
• Beyond 48 hours and still Pending. Raise an iCRP support ticket with the RRR, the iCRP application reference, the bank debit timestamp, and a screenshot of both the Remita Successful confirmation and the bank's debit alert. The CAC support team can manually advance the reconciliation. The typical response window is 24 to 72 hours during working days.

Do not re-attempt the payment from State 1. Remita has already confirmed the funds; a second payment at this stage routes through a fresh RRR, debits the account again, and produces a duplicate that has to be reversed through the bank-Remita-CAC reconciliation route.

The payment is mid-route. Remita has the debit but has not yet flipped the RRR to Successful or Failed.

• Most common timing. Bank-counter payments arrive in Remita's queue 6 to 24 hours after the bank counter accepts the cash, depending on the bank's clearing batch. Card payments through the portal usually flip within minutes; a sustained Remita Pending on a card payment is unusual.
• What to do. Wait the full 48-hour window. Re-check the Remita status every 12 hours; the state will flip to Successful (then State 1 applies) or to Failed (then State 3 applies). Do not generate a fresh RRR and re-pay; the original payment is still routing.
• Beyond 48 hours and still Pending at Remita. Contact Remita support at helpdesk.remita.net with the RRR and the bank-debit timestamp. Remita's reconciliation team can trace where the payment is sitting and advance it or fail it back to the bank for reversal.

A Remita Pending that runs longer than 48 hours is unusual and typically indicates a clearing-cycle issue at the originating bank rather than at Remita itself.

The bank took the money but Remita could not complete the route. The standard recovery is the auto-reversal protocol.

• The auto-reversal. Remita reverses failed transactions to the originating bank within 7 to 10 working days as a matter of standard protocol. The customer typically does not need to initiate the reversal; it lands as a credit to the originating account with a Remita-reversal narrative.
• Keep the evidence. The bank's original debit alert, the Remita Failed status screenshot, and the RRR are the three pieces of paper that re-start the reversal if anything stalls. Save them as soon as you confirm the State 3 diagnosis.
• What to do meanwhile. The CAC application is still alive at iCRP — the registration has not failed, only the first payment attempt. Generate a fresh RRR from the iCRP payment page and pay again, ideally by card on the portal rather than at the bank counter (fewer manual steps, faster reconciliation). The second payment is the one that completes the registration; the first will reverse separately.
• If the reversal does not land within 10 working days. Contact your bank's Remita reconciliation desk. Quote the RRR, the original debit date, and the Remita Failed status. Most Nigerian banks have a dedicated Remita reconciliation desk; ring the bank's customer-care line and ask for it specifically. Open a written complaint if the reconciliation desk does not respond within a further 5 working days.

The temptation to re-pay before the first failure has been confirmed is the most expensive mistake at this stage. Read the Remita status first; only re-pay once the original is confirmed Failed.

The portal generated the reference but the payment never actually started. The recovery is the simplest of the four.

• Confirm no debit. Re-check the bank's SMS, email, and statement covering the time of the original payment attempt. No debit alert and no transaction line on the statement means State 4 applies.
• Check the RRR's validity window. An RRR generated within the last 48 hours is still active; one older than 48 hours has typically lapsed and the bank counter will refuse the payment. The iCRP application page also shows whether the reference is still active.
• If the RRR is still active. Pay against the same RRR. Card payment on the portal is faster; the bank counter is the fallback. The application proceeds normally once the payment confirms.
• If the RRR has lapsed. Generate a fresh RRR from the iCRP payment page. The application reference stays the same; only the payment reference is new. Pay against the fresh RRR.

State 4 is the easy case because no money is in flight. The portal's Pending state simply reflects an unpaid application, not a stuck payment.

Three actions make a stuck payment materially worse, and they come up often enough to flag explicitly.

• Do NOT re-pay before reading the Remita status. The single most expensive mistake in this whole flow is generating a second RRR and paying it against the same application while the first payment is still in flight. The result is two debits, two RRRs, and a reversal cycle that runs 7 to 14 working days.
• Do NOT pay an informal agent on social media or WhatsApp who offers to 'have the payment confirmed' or 'release the hold' for a fee. The CAC reconciliation route runs through Remita and the iCRP support channel; there is no informal fast-track. An agent claiming one is selling you nothing.
• Do NOT cancel the iCRP application and start a fresh one to bypass the stuck payment. The cancelled application's reference state stays in CAC's queue; a duplicate application against the same proprietor and proposed name triggers a similarity flag and stalls again.
• Do NOT close the iCRP portal tab between the Remita debit and the success-page redirect. The success page is where the portal binds the payment confirmation to the application reference; losing it complicates the reconciliation trace if the payment subsequently sticks.
• Do NOT pay at a bank counter using a different RRR than the one on the iCRP application. A typo at the bank counter sends the money against someone else's reference; the correction is a bank-Remita reconciliation case that adds days to the recovery.

Most CAC payment-pending cases resolve within the 48-hour reconciliation window without any escalation. The minority that do not need a clear escalation path.

• 48 to 72 hours with Remita Successful and CAC dashboard still Pending. Raise a ticket at iCRP support (Help / Support link inside the portal). Include the RRR, the application reference, the bank debit timestamp, the bank name, and screenshots of the Remita Successful confirmation and the bank's debit alert. CAC's typical response is 24 to 72 hours during working days.
• 48 hours with Remita Pending and no movement. Contact Remita support at helpdesk.remita.net with the RRR and the originating bank's name. Remita's reconciliation team can trace where the payment is held and advance it or fail it back.
• 10 working days from a Remita Failed and no reversal to the bank account. Contact your bank's Remita reconciliation desk. Quote the RRR, the original debit date, the Remita Failed status, and any communication to date. Open a written complaint if no reversal lands within a further 5 working days.
• 30 days of unresolved escalation through CAC and the bank. The Federal Competition and Consumer Protection Commission (FCCPC) has a consumer-complaints channel for financial-services disputes that have stalled at the institutional level; the CBN Consumer Protection Department is the formal external route for the bank's part of the reconciliation. Both are last-resort escalations, not first-line.

Reversal of a failed CAC payment is the norm, not the exception, but it depends on the customer keeping the paper trail. The single most useful habit is screenshotting the Remita confirmation page and the bank's debit alert at the time of the original payment, before anything goes wrong.

Some patterns make a stuck payment much less likely.

• Pay by card on the iCRP portal rather than at a bank counter. Card payments reconcile within minutes for most cases; bank-counter payments add a clearing-cycle of 6 to 24 hours and a manual RRR-entry step at the counter that is the single most common source of reference-typo failures.
• Pay during banking hours (08:00 to 16:00 WAT, Monday to Friday). Weekend and late-night payments are most likely to be caught in inter-bank settlement lag, particularly at month-end and around public holidays when settlement cycles compress.
• Use a personal bank account in your own name. Payments from third-party accounts complicate reconciliation if anything goes wrong, because the bank's reversal cycle routes back to the originating account.
• Screenshot the Remita success page before closing the tab. If anything subsequently sticks, the success-page screenshot is the strongest piece of evidence in the CAC support ticket and in any bank-side reversal claim.
• Generate the RRR and pay against it the same session. RRRs that sit overnight before the payment attempt are more likely to lapse mid-flow because the reference's validity window starts at generation, not at first payment attempt.

Card payment + during banking hours + same-session reference = the lowest-friction CAC payment route. Most stuck-payment cases trace to one of those three breaking down.