Start
Postman
Download the full checkout collection, import it, and hit the same hosts from your machine.
PayInvert Checkout collection
Download collection
One JSON file. Create order, pay, banks, fee, status, verify, refund, invoicing, payment links, and the staging encrypt helper.
Import
- Download the file above.
- In Postman: Import → Upload Files → choose the JSON.
- Open the collection → Variables. Paste your keys.
| Variable | What to put |
|---|---|
checkout-url | Test: https://payment-api-service.dev.payinvert.com. Live: https://payment-api-service.payinvert.com. Same host for checkout and invoicing. |
public-key | Public key from Console → Settings → API Keys. Header api-key on most checkout calls. |
private-key | Secret key. Used on Verify, Refund, and Invoicing. Never a browser or app binary. |
env-id | Header x-env-id on invoice merchant calls. Defaults to 1. |
invoice-reference | Filled by Create Invoice in the collection tests. Used on later invoice calls. |
idempotency-key | Defaults to a new GUID. Required on create and issue. |
Staging encrypt helper
POST /payment/data/encrypt/new exists on the test host only. Folders named Sample Payload to encrypt call it first, then the real route. Do not use that helper against production.
What is inside
- Create order (plain, payment link, recurring)
- Pay with card, saved card, and bank transfer
- Order status, fee, banks (including USSD)
- Verify and refund with the secret key
- Invoicing (create, issue, pay)
- Payment links and tokenized charge
The in-docs test panels still encrypt in the browser. Postman follows the collection scripts: encrypt on staging, then send {{encrypteddata}} to the operation.
A 200 is not settlement
After Pay, call Order status or Verify before you fulfil.