Skip to main content
GET
Fetch a transaction / verify a payment
Answers the question the payment redirect leaves open. Fund and invest sends the buyer to Flutterwave and brings them back to the redirectUrl you supplied, with the outcome appended as query parameters:
That status is the browser’s account of the checkout — it is not proof of payment, and it can be edited by anyone who can edit a URL. Call this endpoint with the tx_ref before you render anything on your return page. Two different things are reported, because they settle at different times: A payment is regularly paid: true, settled: false for a few seconds: the buyer gets back to your page before our webhook has run. Show “payment received, investment processing” and poll this endpoint until settled is true — do not tell the buyer the payment failed. settled: true means the funding is on the books. On a fund-and-invest the token purchase is queued at that moment and completes just after, so the units appear on Member Token Balance a beat later than the wallet credit. If your page confirms the holding rather than the payment, read the balance.
string
required
The tx_ref returned when the payment was initiated (GETXN_FI_…), or the transaction’s own id.
string
The transaction_id from the redirect, when you have it. Saves a lookup. Pass only the one that came back with this tx_ref — it is what gets verified, so an id from a different payment returns that payment’s outcome.

Scope

The reference must belong to you — a transaction of your organisation’s, or a payment you initiated for one of your members. Anything else returns 404, whether or not it exists.
transaction is null and provider carries Flutterwave’s verification, because our webhook has not written the funding yet. Poll until settled is true.

Cancelled or abandoned

The buyer came back with status=cancelled, and Flutterwave has no record of the reference.

Status values

Error responses

A reference for a payment that never reached the provider — a checkout closed before it was submitted — stops being resolvable 24 hours after it was initiated, and returns 404 from then on. Anything the provider has a record of, settled or not, stays resolvable.