Troubleshooting Seev Plus

Most Seev Plus issues come from the active organization, verification state, record status, or a missing prerequisite. Work through the relevant section before retrying an action.

Start with these checks

1. Confirm the organization shown at the bottom of the sidebar.
2. Refresh the page after changing organizations.
3. Check the verification banner and follow its action if one is shown.
4. Confirm the record is still active and has not been paid, cancelled, or expired.
5. Check that the currency and source wallet match the action.

I am seeing the wrong business data

Open the organization selector and choose the correct organization. Stores, customers, invoices, payment links, wallets, verification, API keys, and PINs do not carry over between organizations.

If the correct organization is already selected, refresh once. Do not recreate a record until you confirm it is genuinely missing.

I cannot generate a checkout link

Live invoice and payment-link checkout requires approved organization verification.

Also confirm:

• The invoice has a customer and at least one item.
• The invoice or payment link is not paid or cancelled.
• An earlier checkout link has not already completed payment.
• The amount is greater than zero and uses a supported currency.

Verification is blocked or rejected

• Draft: Continue the remaining modules shown by the verification app.
• Ready for review: No action is required unless Seev requests a change.
• Rejected: Read the reason in the Dashboard banner, choose Update verification, edit the existing prefilled information, and submit again.
• Approved: Refresh Seev Plus if a restricted action does not unlock immediately.

Use the business or contractor email associated with the verification profile. One active verification profile cannot be shared across unrelated emails.

A product cannot be enabled

A public storefront product needs at least one image. Click or drop an image onto the empty thumbnail, wait for upload to finish, then enable the product.

Also check that the product is active and has available stock. Disabled products do not appear in POS or the public store.

A payment link has no copy or QR action

Copy, QR, and active checkout actions disappear when a link is paid, cancelled, expired, or otherwise no longer payable. The previous link may remain visible as a receipt record.

Create a new payment request only when the underlying sale genuinely needs another payment.

A payment is pending

Pending means Seev has not received a final result yet. Do not ask the customer to pay again immediately.

1. Wait for the customer's mobile-money or payment confirmation.
2. Refresh the transaction or source record.
3. Check whether a final status or webhook event arrived.
4. Use the payment reference when comparing Dashboard and customer records.

My balance looks wrong

GHS, USDC, and other wallet balances are separate. Changing the currency view does not convert or merge them.

Confirm the selected organization, selected wallet, transaction status, and currency. A pending payment may not yet be available to withdraw.

My transaction PIN does not work

PINs belong to organizations. A PIN from another organization will not verify. Confirm the active organization and use its PIN.

Avoid repeated guesses. If the current PIN cannot be verified, use the available recovery path rather than creating another organization or PIN.

A payout schedule cannot be saved

Manual payouts do not require a destination. Scheduled payouts require a valid selected destination and approved verification. Check that the destination details belong to the active organization and match its destination type.

An API request fails

Confirm all of the following:

• Developer terms have been accepted for the organization.
• The key belongs to the correct product.
• The key and Dashboard are using the same sandbox or production environment.
• Production verification is approved.
• The secret key was copied when it was first shown and has not been rotated or deleted.
• The request body and URL match the current Checkout API guide.

Use the response status and error message with Errors and Codes. Never expose a secret key or full customer payment data when sharing an error.