Skip to main content

Integration checklist

  1. Open your merchant account in the ZewstPay dashboard, complete verification, and wait for approval.
  2. Keep your secret API key on your server. Check GET /v1/account/processing for the account mode and enabled capabilities.
  3. Use ZewstPay secure collection for payment details. Pass owned tok_ or pi_ IDs when attaching methods to a cus_ customer; subsequent payments use pm_ IDs. Never send card numbers or CVV to the API.
  4. Create payments with integer minor units and an Idempotency-Key. Preserve that key when retrying the same operation. An uncertain outcome requires reconciliation before another attempt.
  5. Exercise authorization, capture, void, full and partial refunds, and payment links in sandbox. Verify ownership isolation with a second account.
  6. Register your HTTPS webhook endpoint through POST /v1/webhooks. Verify X-ZewstPay-Signature against the raw request body and your endpoint secret; deduplicate using the event ID. Acknowledge after durable processing so retries remain safe.
  7. For platform payments, assign approved ZewstPay recipients. Reconcile the original allocations, each refund, fees, and completed bank funding for every recipient.

Contracts and settlement​

ZewstPay returns owned IDs and generic errors. Payment routing and processor credentials remain internal. The API supports tested Stripe-shaped interfaces; changing a Stripe base URL and key does not imply support for every Stripe product or object field. Confirm the supported contract before migrating.

Payment success and settlement approval do not prove bank funding. GET /v1/balance reports reconciliation status and pending amounts. Funds already paid to a merchant bank are not available for another withdrawal. Manual payouts are unavailable.

See the API endpoint guide and SDK guide for integration details.