Flutterwave

Africa: list transactions; verify transaction.

Match provider records to your invoices, orders and finance workflows without moving funds.

Build a flow with Flutterwave Provider API documentation

Source actions

Destination actions

Data types

Validation status

Implemented · fixture tested.

Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.

What you can map

transactions

Verify transaction
Source
Read verification for an existing Flutterwave transaction ID.
List transactions
Source
Read v3 transactions with provider status and currency.

Authentication

Flutterwave v3 secret key

Plans and access

An approved provider account with API access and the required read scopes. Availability depends on the merchant country, product, permissions and provider agreement.

Test environment

Use dedicated provider test credentials where available; credential-backed validation is pending.

Rate limits

Provider/account-specific limits apply. HTTP 429 and Retry-After are handled with bounded retries.

Provider events

Provider events are not ingested by this adapter. Nexra event triggers are not yet available; flows run on demand or on a schedule.

Before you build a flow

Pinned to the documented v3 transactions API; v4 OAuth/payment contracts are separate.
Read only: no charges, transfers, refund creation or payouts.
Sandbox and authorised-account validation pending.