Retrieve a Flutterwave v4 campaign charge
Retrieves the latest provider status for a campaign charge and refreshes the Redis charge state. The controller first validates the charge state against client, program, charge id, and optional session id, then returns the common Flutterwave v4 charge response payload. Public checkout polls this endpoint after redirect, OTP, or 3DS flows.
Path Parameters
Client id stored in the Redis charge state.
Program id stored in the Redis charge state.
Flutterwave charge id to retrieve and use for Redis state lookup.
Optional Redis frontend session id. When supplied, it must match the session stored for the charge.
Response
Current Flutterwave charge status.
The response is of type object.