Gateway credentials — connect your Moniepoint (or Opay / Squad) account

Some payment gateways route through a physical card terminal you own (Moniepoint, Opay, Squad). For those, each merchant uses their own account with the provider — there's no shared pool the way Paystack works. This page is where you paste the Client ID and Client Secret the provider issued you, so charges from this system can talk to your terminal.

Before you start

• You need an account with the provider (e.g. a Moniepoint merchant account) and at least one physical terminal already shipped to your store.
• You must have your provider's API credentials ready. On Moniepoint, you'll find them under Merchant Dashboard → Developer / ERP Integration → API Keys.
• Make sure the ERP Integration toggle is on in your provider dashboard. Without it the provider will reject every charge.
• Moniepoint specifically: the terminal firmware must be v1.7.2 or newer. Older firmware can't accept pushed charges.
• You must have Account Master permission to open this page.

Steps

1. Go to Setup → Gateway Credentials. You'll see a row for each supported provider.
2. Find the provider you're setting up (e.g. Moniepoint) and click Configure.
3. Paste your Client ID (the dashboard sometimes calls it "Merchant ID" or "Public Key").
4. Paste your Client Secret (private, shown on the dashboard only once when first issued).
5. Make sure Active is ticked.
6. Click Test connection. The system calls the provider once to confirm the credentials work. You'll see a green toast ("Credentials accepted") or a red one ("Credentials rejected").
7. If the test passes, click Save. The secret is encrypted before storage — you'll never see it again on the page. To replace it later, just paste a new value over the masked field.

Tips

• The secret field shows "Leave blank to keep existing secret" once saved. So if you only need to update the Client ID or toggle Active, leave the secret field empty.
• You can deactivate a provider temporarily (during a billing dispute, for example) without losing the stored credentials — they stay encrypted and inactive until you toggle Active back on.
• Test the connection before walking away — it's the fastest way to catch a typo. Charges that fail at terminal time produce more confusing error messages.

Common problems

• "Credentials rejected" → most often a copy-paste extra space, or the wrong half of a pair (client_id vs api_key). Open the provider dashboard side-by-side and re-paste from there.
• Test passes, but real charges fail → check that the ERP Integration toggle is still on in the provider dashboard. Some providers silently disable it after long inactivity.
• "Stored secret can't be decrypted" → this means the server's encryption keys rotated since the secret was stored (rare — only happens after major infrastructure work). Re-enter the secret to fix it. You don't need to change anything on the provider's side.
• No "Active" row but I just saved one → make sure the Active checkbox was ticked when you clicked Save; otherwise the row stays in the table but greyed.