Important: Migrate to the SeevPlus Payment Routes
Update direct gateway integrations to use SeevPlus payment routes for more reliable organization-scoped processing.
We’ve introduced SeevPlus payment routes to improve the reliability of payment
processing across organizations. If your integration currently initializes or
verifies payments through gateway-api.seevcash.com, update it to use
api.seevplus.com.
The new routes preserve the gateway request and response contracts, so migration normally requires changing only the endpoint URLs. This ensures SeevPlus can associate each payment with the correct organization and reliably process transaction records, balances, payment alerts, receipts, and downstream payment workflows.
Important: Direct gateway integrations do not automatically provide SeevPlus with the organization context needed for dependable organization-scoped processing. Migrate to the SeevPlus initialization route as soon as practical, especially if your account manages multiple organizations.
Why this migration is important
- Correct organization attribution for accounts managing multiple organizations.
- More reliable successful-payment alerts and receipts.
- More reliable transaction, wallet, and ledger tracking.
- Better reconciliation and payment diagnostics.
- Reduced risk of payments being associated with whichever organization was most recently selected.
- A consistent SeevPlus-controlled integration path for future reliability improvements.
SeevPlus does not change your checkout amount or item calculations. The payment gateway still calculates totals and processes checkout; SeevPlus adds the organization context needed for reliable business processing.
Endpoint changes
| Operation | Previous endpoint | New endpoint |
|---|---|---|
| Initialize payment | POST https://gateway-api.seevcash.com/api/v1/payments/initiate | POST https://api.seevplus.com/api/v1/developer/payments |
| Fetch/verify session | GET https://gateway-api.seevcash.com/api/v1/widget/session/{sessionRef} | GET https://api.seevplus.com/api/v1/developer/payments/{sessionRef} |
Minimal migration example
Before:
const response = await fetch(
'https://gateway-api.seevcash.com/api/v1/payments/initiate',
options,
);After:
const response = await fetch(
'https://api.seevplus.com/api/v1/developer/payments',
options,
);Keep the rest of your initiation request the same:
- Keep the existing POST request body.
- Keep the existing checkout API key.
- Keep existing response parsing, including
data.checkout_url. - Keep existing amount/item calculations and smallest-unit conventions.
- Change the initialization URL.
- Change the verification URL.
- Do not manually add SeevPlus organization metadata.
- Test both successful and failed payments after migration.
Migration checklist
- Replace the payment initialization URL.
- Replace the session verification URL.
- Confirm the existing checkout API key is still sent on POST.
- Confirm the POST body is unchanged.
- Confirm redirects still use
data.checkout_url. - Confirm server-side verification uses the new GET route.
- Test amount-based checkout.
- Test itemized checkout.
- Confirm successful payments appear under the correct organization.
- Confirm successful-payment alerts reach the correct recipient.