Remita Nigeria Government and Business Payment API
Remita Nigeria payment REST API for businesses and government agencies to accept payments, process payroll, manage direct debit mandates, and handle government fee collection through Nigeria's government-endorsed payment infrastructure, used for federal and state government collections (GIFMIS), IPPIS payroll processing, and enterprise payment management. Enables AI agents to manage payment initiation for Nigeria e-commerce and bill payment automation, handle direct debit mandate for Nigeria recurring payment automation, access government levy and fee collection for Nigeria government payment automation, retrieve payment status for Nigeria transaction confirmation automation, manage payroll processing for Nigeria IPPIS-connected payroll automation, handle split payment for Nigeria marketplace disbursement automation, access bank transfer for Nigeria multi-bank payment automation, retrieve transaction reporting for Nigeria reconciliation automation, manage refund processing for Nigeria order management automation, and integrate Remita with Nigerian government, enterprise, and business platforms for end-to-end Nigeria payment and payroll automation.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Nigeria government payment. CBN, NDIC. SHA-512 hash. NG. Payment and mandate data.
⚡ Reliability
Best When
A Nigerian enterprise, government agency, or large business wanting AI agents to automate payment collection, direct debit mandates, government fee processing, and payroll through Remita's government-endorsed Nigeria payment infrastructure.
Avoid When
RRR (REMITA RETRIEVAL REFERENCE) IS REQUIRED FOR ALL PAYMENTS: Remita generates a unique RRR for each payment which consumer presents to make payment; automated payment flow must generate and provide RRR to consumer; automated direct charge without RRR generation creates no Remita payment pathway. PAYMENT IS CONSUMER-INITIATED — NOT MERCHANT CHARGE: Remita payment model uses RRR generation then consumer-initiated payment (via bank, USSD, or Remita portal); automated direct merchant card charge is not Remita's primary model; automated assuming card-charge API model creates wrong integration path. DIRECT DEBIT MANDATE REQUIRES SIGNED CONSENT: Remita direct debit requires consumer mandate consent (signed or digital approval); automated recurring debit must complete mandate setup; automated direct debit without mandate creates unauthorized_debit rejection. TESTING REQUIRES DEMO ENVIRONMENT: Remita has specific demo environment (demo.remita.net) separate from production; automated testing must use demo credentials and URL; automated production URL in testing creates unintended production API calls.
Use Cases
- • Collecting government agency fees via Remita for Nigeria federal service agents
- • Processing direct debit mandates for Nigeria loan repayment automation agents
- • Accepting online payments for Nigeria e-commerce and services checkout agents
- • Managing IPPIS-connected payroll for Nigeria government payroll automation agents
Not For
- • Non-Nigeria payments (Remita is Nigeria-focused infrastructure)
- • Simple consumer app integration (Remita is enterprise and government infrastructure)
- • International cross-border transfers (Remita is Nigerian domestic payment focus)
Interface
Authentication
Remita uses merchantId + serviceTypeId + SHA-512 hash authentication. REST API with JSON. Lagos, Nigeria HQ. SystemSpecs subsidiary. Founded 2005 by John Obaro. Products: Payment gateway, direct debit, government collections (GIFMIS), IPPIS payroll, corporate banking portal. SDKs: JavaScript, PHP, Java, .NET. CBN-licensed. NDIC member. Used by Nigerian federal government for IPPIS and GIFMIS. 20M+ transactions/year. Competes with Interswitch for Nigerian government and enterprise payments.
Pricing
Lagos NG. SystemSpecs. Per-transaction fees capped in NGN. CBN licensed. Government-endorsed.
Agent Metadata
Known Gotchas
- ⚠ SHA-512 HASH AUTHENTICATION: Remita auth uses SHA-512(merchantId + serviceTypeId + orderId + totalAmount + apiKey) as authorization hash header; automated request must compute per-request SHA-512 hash; automated static API key header without hash creates unauthorized error
- ⚠ RRR GENERATION IS PREREQUISITE TO PAYMENT: Remita payment flow requires generating RRR first (POST /exapp/api/v1/send/api/lookuprequest); automated payment must generate RRR and provide to consumer; automated direct card charge without RRR creates wrong integration model
- ⚠ DEMO ENVIRONMENT IS SEPARATE URL: Remita demo is at demo.remita.net not remita.net; automated sandbox testing must use demo URL and demo credentials; automated test with production URL creates live payments in test
- ⚠ DIRECT DEBIT MANDATE STATUS POLLING: Remita direct debit mandate approval requires polling mandate status after sending to consumer; automated recurring payment must confirm mandate is active before first debit; automated immediate debit without mandate confirmation creates debit_before_mandate_active
- ⚠ NOTIFICATION URL FOR ASYNC PAYMENT: Remita payment completion is delivered to notificationUrl; automated payment system must register notificationUrl; automated polling-only payment confirmation creates delayed status awareness
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Remita Nigeria Government and Business Payment API.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-07.