mpesa), SasaPay (sasapay) or Paystack (paystack). Each business has one collection rail and one payout rail. Your code doesn’t change when the rail changes: you always call the same endpoints, and the response’s provider and method say which rail did the work.
What each rail can do
Ask for a network the rail can’t prompt and you get
400 network_unsupported before anything is sent.
Prompt a phone on any network
Sendnetwork with the collection. Leave it out for M-Pesa.
GET /v1/merchants/{id}/rails (below) once at start-up.
Card checkout (Paystack)
With a Paystack rail incheckout or both mode, send method: "checkout". The phone number is optional.
checkout_url in the response (it appears while the payment is initiated or pending), then poll as usual.
See and change your rails
GET /v1/merchants/{id}/rails (scope read) shows each service’s provider, whether it is enabled and which providers you may choose:
rails scope:
paystack_mode is charge (phone prompts only), checkout (card page only) or both. With charge or both, a plain collection prompts the phone; with checkout only, it opens a card page.
Whose provider account?
custody says whose account the money passes through:
platform: Cloudpay’s own provider accounts. Nothing to set up; this is the default.byok: your own provider keys (bring your own keys), set under Settings → Rails orPUT /v1/merchants/{id}/credentials/{provider}. Keys are write-only: Cloudpay never returns them.