Create the legacy fixed Flutterwave setup charge
Legacy authenticated card-setup transport. The server always submits an actual USD10 card charge with a generated tx_ref and the current organization’s subaccount, ignoring caller amount/currency. Optional authorization is forwarded to the provider. Returns provider success JSON or local400 with the provider message. Requires an existing organization subaccount. Requires permission: one of access_payment_gateways.
Authorizations
Passport bearer token authentication for legacy admin sessions.
Body
Validated request fields for this operation.
Card number supplied through the authorized card-entry flow.
"EXAMPLE-CARD-NUMBER"
Three/four-character security code.
3 - 4"000"
Two-character expiry month.
2"12"
Two-character expiry year.
2"30"
Cardholder full name.
"Jane Donor"
Cardholder receipt email.
"jane@example.org"
Optional provider authorization payload; forwarded without nested validation.