Payment Methods

Mobile money is the only method that can take a live payment today. Open a checkout link yourself to see what a given payer will be offered, since the methods on the page vary with the checkout type, the currency and the organization's eligibility.

Accept a mobile money payment

On a supported Ghana cedi checkout, the customer picks mobile money and pays from a wallet on one of the networks shown. What happens on their side:

1. They open the payment link and choose mobile money.
2. They enter the phone number registered with their network.
3. They select the network.
4. They continue, and approve the prompt that arrives on the phone.
5. Seev waits for the provider's final result and updates the payment status.

Tell them to keep the phone nearby, unlocked and on the network, and not to restart the payment while the first attempt is still pending. A second attempt started before the first resolves is a second charge, not a replacement for the first.

Accept a USSD payment from your backend

USSD is a server-side flow available through the Checkout API, not a button on a hosted page. Send channels: ["ussd"] as the only channel, along with the customer's phone and a network of MTN, VODAFONE or AIRTEL. Seev returns a USSD intent rather than a checkout_url, so nothing redirects the customer back to you and your integration has to poll the session until it reaches a final status. The full request shape and the intent response are on the Checkout API page.

Payment links, invoices and storefront checkout are unaffected by this. They continue to show whatever the hosted checkout page has enabled.

Check what a method can do today

Dashboards and previews show the unavailable methods as upcoming, which is easy to read as available. Quote a customer only what you saw selectable on the checkout you opened.

Resolve a mobile money prompt that never arrived

The payment sits at pending and the phone stays quiet. Ask them to confirm the number and network they entered, check signal and account standing, and wait briefly in case the provider is slow. Refresh the payment status before anyone retries.

If the attempt has moved to failed, the customer can safely start a new one. If it is still pending, do not create another payment request. A pending attempt can still complete, and two live attempts means the customer can be charged twice.

Handle a customer who says they paid while Seev shows pending

Do not fulfil on the strength of a phone screenshot. Refresh the Seev record and wait for a completed status, then match the Seev payment reference against the source invoice, payment link, order or API transaction before you release anything. A provider confirmation on the customer's handset can precede the final result Seev receives.

If the status has not resolved after a reasonable wait, quote the payment reference to support rather than creating a replacement request.

Test both outcomes in sandbox

Sandbox checkout moves no money and offers explicit success and declined actions, so you can exercise a failed payment as deliberately as a successful one. A sandbox result is never evidence of a live payment.

Checklist before you share a checkout

• Confirm the checkout currency is the one you intend to charge in.
• Open the checkout once and note which methods are actually selectable.
• Tell the customer to use the number registered with their mobile money network.
• For direct USSD, send a matching phone and network, and do not combine ussd with another channel.
• Wait for a final status before fulfilling or creating another request.
• Keep the payment reference to hand for any investigation.

Related guides

• Get Paid with Seev Plus
• Verify a payment
• Payment troubleshooting