otherapi_key

Paystack

Nigerian financial technology company that offers payment processing services to businesses in Africa.

Verdict

The Paystack MCP lets your team manage payments, transfers, and commerce operations directly from Switchy. @mention it to create payment links, check transaction status, add products to storefronts, configure split payments across subaccounts, or bulk-create transfer recipients. Sales and finance teams get the most value — they can generate invoices, verify payments, and reconcile transfers without leaving the conversation. You'll need a Paystack API key with appropriate permissions; some operations (like split management or virtual terminals) require a Nigerian business account.

Common use cases

  • Generate payment links during sales calls
  • Check transaction status before fulfillment
  • Add products to storefront from inventory chat
  • Configure split payments for partner deals
  • Bulk create recipients for payroll transfers

Integration

Vendor
Paystack
Category
other
Auth
API_KEY
Tools
50
Composio slug
paystack

Tools

  • Add Products to Page

    Tool to add products to a Paystack payment page. Use when you need to add products to an existing page that was created with 'product' type. This action adds the specified products to the page, allowing customers to select from multiple pro

  • Add Products to Storefront

    Tool to add previously created products to a Storefront. Use when you need to associate existing products with a specific storefront.

  • Add Split Code to Virtual Terminal

    Tool to add a split code to a virtual terminal. Use when you need to assign payment splitting configuration to a virtual terminal.

  • Add Subaccount to Split

    Tool to add a subaccount to a split configuration, or update the share of an existing subaccount. Use this when you need to modify the payment distribution by adding new partners/customers to a split or adjusting their allocation. The split

  • Archive Payment Request

    Tool to archive a payment request to clean up records. Use when you need to remove a payment request from active listings. An archived payment request cannot be verified and will not appear when listing payment requests.

  • Assign Destination to Virtual Terminal

    Tool to assign WhatsApp destinations to a Virtual Terminal for payment notifications. Use when you need to add recipients who will receive notifications for payments made through a specific Virtual Terminal.

  • Bulk Create Transfer Recipients

    Create multiple transfer recipients in batches. Use when you need to add multiple recipients at once for transfers. Duplicate account numbers automatically return existing recipient records instead of creating duplicates.

  • Check Pending Charge

    Tool to check the status of a pending charge transaction. Use when you receive a 'pending' status from a charge endpoint or need to verify if a charge status has changed. Wait at least 10 seconds after initiating a charge before calling thi

  • Check Slug Availability

    Tool to check if a custom slug is available for use when creating a payment page. Use when you need to verify a slug is not already taken before creating a new payment page.

  • Create Charge

    Tool to initiate a payment by integrating the payment channel of your choice. Use when you need to charge a customer using authorization code, bank account, mobile money, or USSD.

  • Create Customer

    Tool to create a customer on your Paystack integration. Use when you need to add a new customer with their email address and optional details like name and phone number.

  • Create Payment Page

    Tool to create a payment page on your Paystack integration. Use when you need to create a payment page that customers can visit to make payments.

  • Create Payment Request

    Create a new payment request by issuing an invoice to a customer. Use this when you need to request payment from a customer for goods or services.

  • Create Plan

    Tool to create a plan for recurring payments on Paystack. Use when you need to set up subscription billing or recurring payment schedules. The plan defines the amount, interval, and other settings for recurring charges to customers.

  • Create Refund

    Tool to initiate a refund for a previously completed transaction on Paystack. Use when a customer requests a refund or when you need to reverse a payment. The refund can be for the full transaction amount or a partial amount.

  • Create Split Configuration

    Tool to create a split configuration for transaction revenue sharing. Use when you need to configure how transaction revenue should be split between multiple subaccounts (e.g., for marketplace platforms, revenue sharing, or commission distr

  • Create Storefront

    Create a digital storefront on Paystack to manage and display products. Use this when you need to set up a new online shop for selling digital or physical products.

  • Create Subaccount

    Tool to create a subaccount on your Paystack integration. Use when you need to set up a new subaccount with bank details and settlement information.

  • Create Transfer Recipient

    Tool to create a new recipient for transfers. Use when you need to set up a recipient before initiating a transfer. Note: A duplicate account number will lead to retrieval of the existing record rather than creating a new one.

  • Create Virtual Terminal

    Create a Virtual Terminal on your Paystack integration to accept payments. Use this when you need to set up a new payment terminal for in-person or remote transactions with custom notification settings.

  • Deactivate Authorization

    Tool to deactivate an authorization when a card or payment method needs to be forgotten. Use when customers want to remove saved payment methods from their account.

  • Deactivate Virtual Terminal

    Tool to deactivate a Virtual Terminal on your integration. Use when you need to disable a terminal and prevent it from accepting further payments.

  • Delete Product
    destructive

    Delete a previously created product from Paystack by its ID. Use this when you need to remove a product from your catalog. The deletion is permanent and cannot be undone.

  • Delete Storefront
    destructive

    Delete a previously created storefront from Paystack by its ID. Use this when you need to remove a storefront. The deletion is permanent and cannot be undone.

  • Delete Transfer Recipient
    destructive

    Tool to delete a transfer recipient by setting it to inactive status. Use when you need to remove a recipient from the active transfer list.

  • Disable OTP for Transfers

    Tool to disable OTP requirement for programmatic transfers. Use when you want to complete transfers without OTP verification. Returns an OTP needed to finalize the request.

  • Disable Subscription

    Tool to disable a subscription on your Paystack integration. Use when you need to stop recurring charges for a customer subscription. Requires the subscription code and email verification token sent to the customer.

  • Duplicate Storefront

    Tool to duplicate a previously created Storefront. Use when you need to create a copy of an existing storefront with the same configuration.

  • Enable OTP for Transfers

    Tool to enable OTP requirement for transfers. Use when a customer wants to stop being able to complete transfers programmatically and require OTP verification instead.

  • Export Transactions

    Tool to export transactions from Paystack for a specific timeframe. Use when you need to download transaction data for reporting, analysis, or record-keeping purposes. The API returns a download link that expires after a certain time.

  • Fetch Balance

    Tool to fetch the available balance on your Paystack integration. Use when you need to check account balance across different currencies.

  • Fetch balance ledger

    Tool to fetch all pay-ins and pay-outs that went into your Paystack balance. Use when you need to view transaction history and balance changes over time.

  • Fetch Bulk Charge Batch

    Tool to retrieve a specific bulk charge batch by code. Use when you need to check the progress of a bulk charge batch via its total_charges and pending_charges attributes.

  • Fetch Customer

    Tool to get details of a customer on your integration. Use when you need to retrieve customer information using their customer code.

  • Fetch Mandate Authorizations

    Tool to fetch the list of direct debit mandate authorizations associated with a customer. Use when you need to retrieve all mandate authorizations for a specific customer ID.

  • Fetch Payment Page

    Tool to fetch details of a payment page on your Paystack integration. Use when you need to retrieve information about a specific payment page by its ID.

  • Fetch Payment Request Details

    Tool to fetch details of a payment request from Paystack. Use when you need to retrieve comprehensive information about a previously created payment request, including customer details, payment status, line items, and associated metadata.

  • Fetch Payment Session Timeout

    Tool to fetch the payment session timeout configured on your Paystack integration. Use when you need to check the current timeout duration for payment sessions.

  • Fetch Plan

    Tool to get details of a plan on your integration. Use when you need to retrieve plan information using the plan code or ID.

  • Fetch Product

    Tool to get details of a product on your integration. Use when you need to retrieve product information by its ID.

  • Fetch Product Orders

    Tool to fetch all orders for a particular product on your Paystack integration. Use when you need to retrieve order history and details for a specific product by its ID.

  • Fetch Refund

    Tool to get details of a refund on your integration. Use when you need to retrieve comprehensive information about a specific refund, including status, amount, customer details, and timestamps.

  • Fetch Split

    Tool to get details of a split configuration for a transaction. Use when you need to retrieve split payment configuration information by its ID.

  • Fetch Storefront

    Tool to get the details of a previously created Storefront. Use when you need to retrieve information about a specific storefront including its products, contacts, and configuration.

  • Fetch Storefront Orders

    Tool to fetch all orders in a Paystack storefront. Use when you need to retrieve order information for a specific storefront using its ID.

  • Fetch Subaccount

    Tool to get details of a subaccount on your integration. Use when you need to retrieve subaccount information using the subaccount code.

  • Fetch Subscription

    Tool to get details of a subscription on your integration. Use when you need to retrieve subscription information using the subscription code.

  • Fetch Transaction

    Tool to get details of a transaction carried out on your integration. Use when you need to retrieve comprehensive information about a specific transaction, including payment status, customer details, authorization info, and timestamps.

  • Fetch Transaction Timeline

    Tool to fetch the timeline of a transaction showing the steps taken from initiation to completion. Use when you need to debug payment flows or understand where customers encountered issues during the payment process.

  • Fetch Transfer Recipient

    Tool to fetch details of a transfer recipient. Use when you need to retrieve information about an existing recipient using their recipient code.

Setup

Setup guide

  1. 11. In Switchy, open your workspace settings and navigate to the MCP integrations section. 2. Select 'Add MCP' and choose Paystack from the list. 3. Log into your Paystack dashboard, go to Settings > API Keys & Webhooks, and copy your Secret Key (starts with 'sk_'). 4. Paste the key into Switchy's connection form and click 'Connect'. 5. Switchy will verify the key works by making a test API call. 6. Once connected, open any Space and type '@Paystack check my last 5 transactions' to confirm the integration responds. 7. The MCP can now access all tools your API key permits — if you need split payments or virtual terminal features, ensure your Paystack account has those enabled in your dashboard.

What teammates see: by default, memories from Paystack 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

Verify Recent Payment

@Paystack check the status of transaction reference TRX_abc123xyz and tell me if it's successful
Open in a Space →

Add Storefront Products

@Paystack add product IDs prod_001 and prod_002 to storefront store_main
Open in a Space →

Configure Payment Split

@Paystack add subaccount sub_partner01 to split code SPL_xyz with 25% share
Open in a Space →

Bulk Add Recipients

@Paystack create transfer recipients for these accounts: John Doe 0123456789 GTBank, Jane Smith 9876543210 Access Bank
Open in a Space →

Example outputs

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

Prompt

@Paystack show me all payment requests created in the last 30 days that are still pending, grouped by customer

Output

Based on your Paystack account data, here are the pending payment requests from the last 30 days: **Customer: Acme Corp** (2 requests) - PR_abc123: ₦50,000 for Q1 Invoice, created Jan 15 - PR_def456: ₦75,000 for Consulting Services, created Jan 28 **Customer: Beta Industries** (1 request) - PR_ghi789: ₦120,000 for Annual License, created Jan 10 Total pending: ₦245,000 across 3 customers. All requests were sent via email and have not been paid yet. This is an illustrative summary—actual request counts and amounts will vary based on your account activity.

Notes

This example demonstrates Paystack's read capabilities for payment request tracking. Requires API key with read access to payment requests. The MCP can filter by date ranges and status, making it useful for accounts receivable monitoring. Note that customer grouping depends on how payment requests were originally tagged in your Paystack account.

Prompt

@Paystack create a new transfer recipient for vendor payments: account number 0123456789, bank GTBank, name 'Supplier XYZ Ltd'

Output

Transfer recipient created successfully: **Recipient Code:** RCP_xyz789abc **Account Name:** Supplier XYZ Ltd **Account Number:** 0123456789 **Bank:** Guaranty Trust Bank (GTBank) **Status:** Active This recipient is now available for transfers. You can reference it using the recipient code RCP_xyz789abc when initiating payouts. The account details have been verified with the bank. This is an illustrative example—actual recipient codes and verification results depend on the bank's response.

Notes

This showcases Paystack's write capability for managing transfer recipients, essential for vendor payment workflows. The MCP validates account details with Nigerian banks in real-time. Requires API key with write permissions. Be aware that invalid account numbers will fail verification, and some banks may have slower verification times during peak hours.

Prompt

@Paystack analyze my transaction success rates by payment channel over the last quarter and suggest which channels I should prioritize

Output

Here's your Q1 2024 payment channel performance analysis: **Card Payments:** 847 transactions, 94.2% success rate, ₦12.4M volume **Bank Transfer:** 312 transactions, 98.7% success rate, ₦8.9M volume **USSD:** 156 transactions, 89.1% success rate, ₦2.1M volume **Mobile Money:** 89 transactions, 91.0% success rate, ₦1.3M volume **Recommendation:** Bank transfers show the highest success rate and strong volume. Consider promoting this option more prominently at checkout. Card payments have the highest volume but lower success—investigate declined transactions for patterns (insufficient funds, expired cards). This analysis is illustrative based on typical Paystack metrics.

Notes

This example pairs Paystack's transaction data retrieval with AI reasoning to generate actionable insights. The MCP fetches raw transaction records, and the AI performs the success rate calculations and strategic recommendations. Useful for optimizing payment flows, but remember that channel performance varies by customer demographics and transaction amounts in your specific business context.

Use-case deep-dives

Multi-vendor marketplace payout automation

When Paystack wins for splitting revenue across sellers

A 6-person e-commerce team running a marketplace with 40+ vendors needs to automate payouts every Friday. Paystack's split and subaccount tools handle this scenario cleanly: you create one split configuration per vendor cohort, add subaccounts as sellers onboard, and trigger bulk transfers when orders settle. The 'Add Subaccount to Split' and 'Bulk Create Transfer Recipients' tools let you script the entire flow in Switchy without touching the Paystack dashboard. This works until you hit roughly 200 vendors—at that scale, the 50-tool limit starts to feel constraining because you're juggling splits, storefronts, and payment pages in the same workspace. If your marketplace is still under 100 sellers and you're doing weekly payouts, Paystack's MCP is the right call.

Subscription SaaS payment request tracking

Why this MCP falls short for high-volume invoicing

A 3-person B2B SaaS team sends 500+ payment requests monthly to enterprise customers who prefer invoices over card-on-file. Paystack's 'Archive Payment Request' and 'Check Pending Charge' tools exist, but the MCP doesn't expose batch-status checks or webhook-driven updates—you're polling one request at a time. If you're reconciling payments in Switchy during month-end close, you'll spend more time waiting on API calls than you save by avoiding the dashboard. The threshold here is around 50 requests per week: below that, manual checks are tolerable; above it, you need a webhook listener or a dedicated finance tool. For low-volume SaaS (under 100 customers, mostly annual contracts), the MCP works fine for ad-hoc lookups.

Physical retail virtual terminal setup

When Paystack's terminal tools simplify in-person checkout

A 2-person retail operation with three pop-up locations needs to take card payments without a full POS system. Paystack's 'Add Split Code to Virtual Terminal' and 'Assign Destination to Virtual Terminal' tools let you configure WhatsApp notifications and revenue splits (e.g., 10% to the venue) directly from Switchy before each event. You create a terminal, assign the split, add the venue owner's phone number, and you're live in under five minutes. This scenario assumes you're doing under 200 transactions per location per month—beyond that, you'll want a dedicated POS with inventory sync. For pop-ups, markets, or low-volume brick-and-mortar, the MCP gives you payment infrastructure without the overhead of a full retail stack.

Frequently asked

What can Switchy do with the Paystack MCP?

Switchy can manage your entire Paystack payment infrastructure through AI — create payment pages and storefronts, add products, configure split payments across subaccounts, send payment requests, bulk-create transfer recipients, and check transaction statuses. It's useful for teams that need to automate payment operations or let non-technical staff handle Paystack tasks without touching the dashboard.

Do I need admin access to connect Paystack?

You need a Paystack API key with the appropriate permissions for the operations you want to run. Paystack uses secret keys (for server-side operations) and public keys (for client-side). For Switchy, you'll typically use a secret key since most of the 50 tools perform backend actions like creating recipients or archiving requests. Check your Paystack dashboard under Settings > API Keys & Webhooks.

Can the MCP process refunds or cancel transactions?

The MCP focuses on payment setup and recipient management — creating pages, adding products, configuring splits, and checking charge statuses. Refunds and cancellations aren't in the representative tool list, so you'll likely need to handle those directly in the Paystack dashboard or via their API. The MCP is strongest for automating the pre-transaction and post-transaction recipient workflows.

How is this different from just using Paystack's dashboard?

The dashboard requires manual clicks for every payment page, product addition, or split configuration. Switchy lets you describe what you need in plain language — 'add these five products to the storefront' or 'create transfer recipients for this CSV' — and the AI executes the Paystack API calls. It's faster for bulk operations and lets non-developers handle payment ops without learning Paystack's interface.

Who on the team should connect the Paystack MCP?

Whoever owns your Paystack account and has access to generate API keys — usually a finance lead, ops manager, or technical founder. Once connected, you can share the Switchy workspace with customer support or sales reps who need to create payment links or check transaction statuses, without giving them full Paystack dashboard access. The API key permissions control what actions are possible.

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