callCash()by riverrr
Get early access

callCash() / API

Seven endpoints. Planned, not built yet.

This is the hosted API we are building: plain HTTP verbs and amounts in rand, the same calls on every gateway. Until it exists, the callcash package does the same job inside your own server.

Planned

The hosted API and cc_test_ / cc_live_ keys don’t exist yet, so nothing on this page answers today. What works now is the callcash package on your own Yoco and Netcash keys. Read the docs.

POST/v1/payments
curl https://callcash.riverrr.co.za/v1/payments \
  -u cc_test_9fK2…: \
  -d amount=250 \
  -d reference=order_1042 \
  -d email=lerato@example.co.za
201response
{
  "id": "pay_8Kx2",
  "status": "pending",
  "amount": 250.00,
  "currency": "ZAR",
  "reference": "order_1042",
  "gateway": "netcash",
  "checkout_url": "https://callcash.riverrr.co.za/c/pay_8Kx2"
}

Keys

Planned: cc_test_ keys that never move money, and cc_live_ keys that switch on once your gateway approves you. Same code, different key. Today, the package’s built-in test gateway needs no key at all.

Safe to retry

Send an Idempotency-Key header on anything that creates. Retry as often as your network needs; the customer is charged once.

Rand, not cents

amount: 250 means R250.00. Two decimals at most, checked on our side before any gateway sees it.

Errors you can read

Every error names what went wrong and what to do next. No gateway codes passed through raw. The package uses the same codes today: see the full list.

NextCheckoutWhat your customer sees when the call runs.