Run a charge activity against a payment request.
Creates an activity on the ugwo. The activity describes one attempt to act on the payment — today the only supported type isDocumentation Index
Fetch the complete documentation index at: https://docs.kwugwo.africa/llms.txt
Use this file to discover all available pages before exploring further.
charge,
which sends the ugwo to a PSP through the medium you specify.
Activities are independent: a single ugwo can host many of them. If
a mobile_money charge fails, you can immediately create a
bank_transfer activity on the same ugwo without recreating it.
ugw.XXXX.YYYY....charge is supported.data.medium selects the payment medium,
and the rest of the keys inside data are the parameters for that
medium (see Medium parameters below).data.medium is one of bank_transfer, ussd, or mobile_money.
The other keys inside data depend on which one you picked.
DATE_ATOM) timestamp for when the virtual account
should stop accepting transfers. Optional — defaults to 15
minutes from now. Must be in the future and no more than
15 minutes ahead; timestamps in the past or further out
than 15 minutes return 422.act.…).charge for this endpoint.requires_action when the customer has
more to do (bank transfer, USSD), processing when handed off to
the PSP without further customer input, or failed on a
synchronous error.uid, the currency as [code, label], and the configured
mediums.null for one-off mediums like bank_transfer.paystack_ng.next_action shape.next_action shapebank_transfer, next_action.type is user_action and the
headers block carries everything the customer needs to complete
the transfer (account number, bank name, expiry, amount).