Initialize a Flutterwave v4 order charge
Starts the direct-card Flutterwave v4 charge flow for the Redis checkout order page. The controller validates email and card or saved-payment-method input, totals saved entity and designation cart values from Redis, adds configured processing fees when requested, creates or reuses Flutterwave customer/payment method records, stores charge state, and returns the common charge response. The session cart must contain at least one saved entity or designation amount.
Path Parameters
Client id that owns the checkout order and gateway configuration.
Program id or hyphen-separated program ids for checkout and settings lookup; selected programs must share the same donor form.
Optional Redis frontend session id containing saved checkout cart hashes and used to store charge state.
Body
Order checkout card details or saved payment method. Amount is computed from Redis cart state rather than a request amount field.
Donor email. Validator rule: required|email.
"jane@example.org"
Payment method family. Validator rule: required|string|in:credit_card.
credit_card "credit_card"
Saved Flutterwave payment method id. When present it replaces card field requirements and must belong to a verified session donor.
"pm_123"
Card number required when payment_method is absent. Alias number is normalized to this field.
"5531886652142950"
Card CVV required when payment_method is absent.
"564"
Two-digit card expiry month required when payment_method is absent.
"09"
Two-digit card expiry year required when payment_method is absent.
"32"
When truthy and program settings contain processing_percentage, the computed Redis cart total is increased by that fee.
true
Legacy alias for processing-fee opt-in.
true
Legacy alias for processing-fee opt-in.
true
Response
Flutterwave order charge initialized.
The response is of type object.