otherapi_key

Flutterwave

Flutterwave is a payments technology company that provides payment infrastructure and APIs enabling businesses to accept and send payments in Africa and globally.

Verdict

Flutterwave MCP connects your Switchy workspace to Africa's largest payment infrastructure. @mention it to create virtual account numbers for customers, generate payment links on the fly, set up recurring billing plans, or manage transfer beneficiaries — all without leaving your conversation. Finance teams use it to handle payment ops in Slack-style chat instead of logging into dashboards. You'll need a Flutterwave API key with appropriate permissions. The MCP exposes 24 tools covering payments, transfers, subaccounts, and virtual accounts, but won't handle disputes or compliance workflows.

Common use cases

  • Generate payment links during sales calls
  • Create virtual accounts for new customers
  • Set up recurring billing for subscriptions
  • Add transfer beneficiaries before payouts
  • Disable expired payment links in bulk

Integration

Vendor
Flutterwave
Category
other
Auth
API_KEY
Tools
24
Composio slug
flutterwave

Tools

  • Create Beneficiary

    Tool to create a new transfer beneficiary. use when you need to add a beneficiary before making a transfer.

  • Create Bulk Virtual Account Numbers

    Tool to create multiple virtual account numbers. use when you need to generate multiple static virtual accounts for customers in a single request.

  • Create Payment Link

    Tool to create a hosted payment link. use when you need a shareable payment url for one-time transactions.

  • Create Payment Plan

    Tool to create a new payment plan. use after confirming plan and customer details.

  • Create Subaccount

    Tool to create a new subaccount. use when you need to configure split disbursement accounts.

  • Create Virtual Account

    Tool to create a new virtual account number. use after confirming customer details when assigning a unique account for bank transfers.

  • Delete Beneficiary
    destructive

    Tool to delete a beneficiary by id. use when you need to remove a saved transfer beneficiary by its unique id after confirming the id.

  • Disable Payment Link

    Tool to disable a flutterwave payment link. use when you need to prevent further payments from an existing link after confirming the link is valid.

  • Fetch Beneficiary

    Tool to retrieve details of a specific beneficiary by id. use after obtaining a beneficiary id to fetch its full details from flutterwave.

  • Fetch Subaccount

    Tool to retrieve details of a specific subaccount by id. use when you need full subaccount info after creating or updating splits.

  • Generate Transaction Reference

    Tool to generate a unique transaction reference. use when initiating a new flutterwave transaction requires a unique reference to prevent duplication.

  • Get All Subscriptions

    Tool to retrieve all subscriptions, including cancelled ones. use when you need a comprehensive list of subscription records for auditing or reporting.

  • Get All Wallet Balances

    Tool to retrieve all wallet balances across currencies. use when reconciling balances after authentication.

  • Get Balances per Currency

    Tool to retrieve wallet balance for a specific currency. use after transactions to confirm available and ledger balances in a given currency.

  • Get Bill Categories

    Tool to retrieve available bill categories. use after authenticating to flutterwave to display bill payment options to users.

  • Get Multiple Refund Transactions

    Tool to retrieve multiple refund transactions with optional filters. use when you need to fetch paginated refund data after confirming valid api credentials.

  • Get Payment Plans

    Tool to retrieve a list of all payment plans. use when you need to fetch and present your account’s configured billing plans.

  • Get Transaction

    Tool to retrieve details of a specific transaction by id. use after obtaining the transaction id to fetch its details from flutterwave.

  • Get Transaction Fee

    Tool to retrieve the fee for a specific transaction. use when you need to calculate the total charge including fees before initiating the transaction.

  • Get Transfer Fee

    Tool to retrieve the fee for initiating a transfer. use when you need to estimate transfer costs before creating a transfer. example: "calculate the fee for transferring ngn 5000 to an account."

  • Initiate Mobile Money Tanzania

    Tool to initiate a mobile money payment in tanzania. use after collecting customer details to charge via tanzanian mobile money networks.

  • List All Beneficiaries

    Tool to list all saved beneficiaries. use when you need to retrieve all transfer beneficiaries associated with your account.

  • Retrieve all transactions

    Tool to retrieve a list of all transactions with optional filters. use when you need to paginate or filter transaction history after confirming valid api credentials.

  • View Transaction Timeline

    Tool to retrieve the event timeline for a transaction. use after obtaining the transaction id to audit or track the sequence of events.

Setup

Setup guide

  1. 11. In Switchy, open your workspace settings and navigate to Integrations. 2. Search for Flutterwave and click Connect. 3. You'll be prompted to paste your Flutterwave API key — get this from your Flutterwave dashboard under Settings > API. 4. Choose either your test or live key depending on whether you're experimenting or handling real transactions. 5. Grant the connection and Switchy will verify the key works. 6. Open any Space and type '@Flutterwave' to confirm the integration appears in the mention menu. 7. Test it by asking '@Flutterwave list my recent transactions' — if you see results, you're connected. 8. The API key's permissions determine which tools you can invoke, so ensure your key has scopes for payments, transfers, and virtual accounts if you need those workflows.

What teammates see: by default, memories from Flutterwave are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.

Works well with

Top models

Compatibility data appears once enough Spaces have used this MCP together with a given model.

How Switchy teams use it

Not enough Spaces yet to publish anonymised usage stats (we require ≥ 50 Spaces per week).

Starter prompts

Issue Virtual Account

@Flutterwave create a virtual account for customer email jane@startup.co with name Jane Doe and BVN 22234567890
Open in a Space →

Set Up Payment Plan

@Flutterwave create a monthly payment plan called 'Pro Membership' for 5000 NGN with 12 intervals starting next week
Open in a Space →

Add Transfer Beneficiary

@Flutterwave create a beneficiary named Acme Suppliers with account number 0123456789 at GTBank Nigeria
Open in a Space →

Example outputs

Illustrative - representative of the model's voice and quality, not literal recordings.

Prompt

@flutterwave show me all active payment links created in the last 30 days and their total collected amounts

Output

Based on your Flutterwave account, here are the active payment links from the past 30 days: 1. **Q1 Consulting Invoice** (created Jan 15) — 12 payments, ₦2,450,000 collected 2. **Workshop Registration** (created Jan 22) — 47 payments, $3,290 collected 3. **Product Pre-order Link** (created Feb 3) — 8 payments, ₦680,000 collected All three links remain active. The workshop link accounts for the highest transaction volume. This is an illustrative example showing how the MCP retrieves and summarizes payment link activity.

Notes

This example demonstrates read-only data retrieval across payment links. Requires API key with read permissions for payment links. The MCP returns structured transaction data that the AI can aggregate and summarize. Actual response shape depends on your account's payment history and currency mix.

Prompt

@flutterwave create a virtual account for customer email john.doe@example.com, name John Doe, and phone +2348012345678

Output

Virtual account created successfully for John Doe: **Account Number:** 7845623019 **Bank Name:** Wema Bank **Account Name:** John Doe/YourBusiness **Customer Email:** john.doe@example.com **Status:** Active This account is now live and can receive NGN transfers. Funds will settle to your main Flutterwave balance. Note that this is an illustrative example — actual account numbers and bank assignments vary by availability and your Flutterwave configuration.

Notes

This write operation creates a permanent virtual account tied to a customer. Requires API key with write permissions. The MCP provisions a real bank account number that routes payments to your balance. Be aware that virtual accounts cannot be deleted once created, only deactivated, and some banks may have daily creation limits.

Prompt

@flutterwave create a payment plan called 'Monthly Retainer' for ₦50,000 charged on the 1st of each month, then generate a payment link for the first subscriber

Output

Payment plan and link created: **Plan Details:** - Name: Monthly Retainer - Amount: ₦50,000 NGN - Interval: Monthly (1st of each month) - Plan ID: PLN_abc123xyz **Payment Link:** https://flutterwave.com/pay/monthlyretainer-abc123 This link enrolls customers into the recurring plan. After the first payment, Flutterwave will automatically charge the saved card on the 1st of each month. This example shows how the MCP chains plan creation with link generation for subscription workflows.

Notes

This example combines two write operations to set up recurring billing. Requires API key with permissions for both payment plans and links. The MCP creates the plan infrastructure, then generates a shareable URL. Subscribers must complete initial payment for auto-charging to activate. Plan modifications after customer enrollment may require manual intervention.

Use-case deep-dives

SaaS subscription billing setup

When Flutterwave handles recurring African market payments

A 6-person SaaS startup launching in Nigeria needs to bill 200 customers monthly in naira. Flutterwave's payment plan tool lets you set up recurring charges without building subscription logic from scratch, and the virtual account tool assigns each customer a unique bank transfer number so they can pay without a card. This MCP is the right call if your team is already using Switchy for customer ops and wants payment setup in the same workspace where you handle support tickets. The auth is straightforward API key scope, so any team member can create plans or check payment status without bouncing to the Flutterwave dashboard. If you're processing under 500 transactions a month and your finance person isn't technical, this keeps billing accessible.

Marketplace seller payout automation

Subaccounts and beneficiaries for multi-vendor splits

A 3-person team running a freelance marketplace in Kenya needs to split each project payment between the platform fee and the freelancer's cut. Flutterwave's subaccount tool configures the split percentages, and the beneficiary tools let you save each freelancer's bank details so payouts don't require manual data entry every time. This MCP works when your transaction volume is under 100 splits a week and you're coordinating payouts in Slack or a shared doc. The 24 tools cover edge cases like deleting stale beneficiaries or disabling payment links after a project closes, but if you're doing high-frequency microtransactions or need real-time settlement reporting, you'll hit the rate limits and want a dedicated finance dashboard instead.

Event ticketing payment collection

Payment links for one-off sales without a storefront

A 2-person events team in Ghana is selling tickets to a conference and needs a way to collect payments without building a checkout page. Flutterwave's payment link tool generates a hosted URL you can drop in an email or social post, and the bulk virtual account tool creates unique transfer numbers if attendees prefer bank payments over cards. This MCP is the move if you're running 3-5 events a year and your team already uses Switchy to coordinate vendor contracts and attendee lists. The create and disable link tools mean you can spin up a new payment flow in under a minute and shut it down when ticket sales close. If you're doing weekly events or need custom branding on the checkout page, the hosted link starts to feel generic and you'll want a full Flutterwave integration on your own domain.

Frequently asked

What does the Flutterwave MCP do in Switchy?

It lets your AI agents create payment links, manage virtual accounts, set up subaccounts for split payments, and handle transfer beneficiaries — all without leaving the conversation. Your team can generate a payment URL, assign a customer a unique bank account number, or configure recurring payment plans by asking the AI instead of logging into the Flutterwave dashboard.

Do I need admin access to connect Flutterwave?

You need an API key from your Flutterwave account, which typically requires admin or developer permissions to generate. The key grants full access to the 24 tools, so only connect it if you trust the team members who will use Switchy. Flutterwave doesn't use OAuth — you paste the secret key directly into Switchy's settings.

Can the MCP process actual payments or refunds?

No. It creates payment infrastructure — links, virtual accounts, plans — but doesn't charge cards or move money. A customer still completes the transaction through Flutterwave's hosted checkout or by transferring funds to the virtual account. The MCP also can't issue refunds; you handle those in the Flutterwave dashboard or via their standard API.

Why use this instead of the Flutterwave dashboard?

Speed and context. If you're already discussing a customer issue or campaign in Switchy, the AI can generate a payment link or virtual account mid-conversation. No tab-switching, no copy-paste between tools. The trade-off: you lose the dashboard's visual reports and bulk-edit features, so this works best for one-off tasks, not financial reconciliation.

Who on the team should connect the Flutterwave MCP?

Whoever owns payment operations — usually a finance lead or product manager. Because the API key grants write access to create subaccounts and beneficiaries, don't share it with support reps or contractors unless they need to generate payment links as part of their workflow. One connection covers the whole Switchy workspace.

Data last verified 607 hours ago.Sources aggregated hourly to weekly. See docs/architecture/model-directory.md.