Get Paid with Seev Plus
Choose between invoices, payment links, storefronts, POS, and Checkout API.
Seev Plus gives you several ways to request and accept payment. They use the same hosted checkout experience, but each starts from a different business need.
You do not need to use every option. Start with the simplest one that fits the sale.
If your custom integration still initializes or verifies payments through
gateway-api.seevcash.com, migrate to the SeevPlus payment routes. The new
routes preserve the gateway request and response contracts while adding the
organization context needed for reliable transaction attribution, wallet
processing, alerts, and internal tracking. Read the migration
guide.
Choose the right payment tool
| Your situation | Best option | Why |
|---|---|---|
| You need line items, discount, tax, terms, or a due date | Invoice | Gives the customer a detailed payment request and receipt trail. |
| You only need a customer, amount, and description | Payment Link | Fastest way to create a shareable payment request. |
| Customers should browse products and build a cart | Storefront | Provides a public catalogue, product pages, cart, and orders. |
| A walk-in customer is buying products you select | Storefront POS | Lets the merchant build an in-person order and show a QR or open checkout. |
| Your own app or website should create the payment | Checkout API | Gives your backend control over session creation and verification. |
Before your first live payment
You can prepare invoices, links, products, stores, and sandbox API integrations before approval. To generate a live checkout link or use production API access, the active organization's verification must be approved.
- Confirm the active organization.
- Complete organization verification.
- Create the invoice, link, store order, or API session.
- Review the customer, amount, currency, and description.
- Open the generated checkout once before sharing it.
What the customer experiences
The customer opens a Seev-hosted checkout page showing the merchant, amount, purchase details, and currently available payment methods. After payment, Seev verifies the result and updates the source invoice, link, order, or API transaction.
For POS orders, the payer can provide an email for their receipt without the merchant creating a full customer profile first.
Where the money goes
Successful payments settle into the active organization's available accounts. Open Accounts & Wallets to see real GHS and supported stablecoin balances and transaction activity.
An invoice payment, payment-link payment, store order, POS order, and API payment may appear in different operational tables, but successful funds belong to the same organization that created the payment.
Payment statuses
| Status | What to do |
|---|---|
| Draft | Finish preparing the request before sharing it. |
| Active / Sent | The request is ready for the customer. |
| Pending | Wait for a final confirmation; do not immediately ask the customer to pay again. |
| Paid / Completed | The payment succeeded. Continue fulfilment and retain the receipt record. |
| Failed | Read the reason and let the customer retry when appropriate. |
| Expired | The checkout can no longer accept payment. Create a new request if money is still due. |
| Cancelled | The merchant intentionally stopped the request. It cannot be paid. |
Do not duplicate a payment
Before creating a replacement checkout:
- Refresh the original record.
- Check its current status.
- Search the reference in transaction activity.
- Confirm the customer was not already charged.
Paid records deliberately remove active copy, QR, and checkout-generation actions.
Comparing invoices and payment links
Choose an invoice for formal billing and itemized work. Choose a payment link for a lightweight request. Both can reuse saved customers, generate hosted checkout, and retain a payment record.
Comparing storefront and POS
Use the public storefront when the customer chooses products. Use POS when the merchant chooses products for a walk-in sale. POS orders still appear in Store Orders and are marked separately.
Comparing Dashboard tools and Checkout API
Dashboard tools require no code. Checkout API is for teams that need to start payments from their own application. API integrations require developer terms, product-specific keys, server-side code, payment verification, and webhook handling.