Tools: 13
Payment

Paystack

Connect your account, then chat with AI to run tools.

Paystack is a payment processing platform that enables businesses to accept online and offline payments in Africa. It facilitates secure transactions, invoicing, and financial tracking for merchants.

Use in your AI tool

You’ll sign in to MCPBundles when your client connects.

MCP URL
https://mcp.mcpbundles.com/bundle/paystack

Chat in MCPBundles Studio

This server needs a sign-in. MCPBundles handles that setup once — then chat here with saved access and a log of what ran.

Managed
13 tools
Agent guide included

Opens MCPBundles Studio with this server selected. After sign-in, chat and run tools from the same thread.

Browse all tools

Live probe refreshed Sep 14, 2026 · Endpoint host mcp.mcpbundles.com

AI Skill
SKILL.md

Domain knowledge for Paystack — workflow patterns, data models, and gotchas for your AI agent.

Paystack

Payment processing platform for African markets (Nigeria, Ghana, South Africa, Kenya, Cote d'Ivoire). Handles card payments, bank transfers, mobile money, and USSD. All amounts are in subunits (kobo for NGN, cents for USD/GHS/ZAR/KES) — multiply the base amount by 100.

Entity Hierarchy

Payment Flow
  • Transactions — every payment attempt. States: success, abandoned, failed. Each has a unique reference (your ID) and Paystack id. Contains amount (subunits), currency, channel (card/bank/ussd/mobile_money), customer info, and authorization details for recurring charges.
  • Customers — identified by email (unique). Each customer accumulates transactions, subscriptions, and authorizations. Has customer_code (Paystack ID) and optional metadata.
Recurring Billing
  • Subscriptions — recurring charges linking a customer's authorization to a plan. States: active, non-renewing, attention, completed, cancelled. Has subscription_code, next_payment_date, and email_token for management links.
Financial Operations
  • Invoices (Payment Requests) — billable items sent to customers. States: pending, paid. Can be sent via email or as a link. Each has a request_code and associated offline_reference for offline payments.
  • Transfers — payouts from your Paystack balance to bank accounts. Require a transfer recipient. States: success, pending, failed, reversed. Uses transfer codes.
  • Refunds — partial or full reversal of a successful transaction. Linked by transaction reference.
  • Settlements — batched payouts from Paystack to your bank account. Shows the settlement schedule and deductions.
  • Disputes — chargebacks and payment disputes raised by customers or banks. States: awaiting-merchant-feedback, awaiting-bank-feedback, pending, resolved.

Workflows

  1. Revenue overview: Enumerate transactions filtered by date range → check settlements for payout timing → review disputes for chargebacks.
  2. Customer audit: Enumerate customers → pick one → enumerate their transactions to see payment history.
  3. Subscription monitoring: Enumerate subscriptions → filter by status to find attention or non-renewing subs that need action.
  4. Payout tracking: Enumerate transfers → correlate with settlements to reconcile bank deposits.
  5. Collections: Enumerate invoices (payment requests) → filter unpaid → follow up.
  6. Onboard and bill customer: Create or update a customer → initialize a transaction with their email → share the authorization_url for payment.
  7. Issue refund: Enumerate transactions → find the successful transaction → create a refund (full or partial).
  8. Send payout: Create a transfer recipient with bank details → initiate a transfer from your balance to that recipient.

Pagination

Offset-based with integer page (1-indexed) and perPage (default 50, max 200). Response includes meta.total, meta.page, meta.pageCount. Use page=2, page=3 etc. to paginate — NOT cursor tokens.

Gotchas

  • Amounts in subunits: NGN 100 = 10000. Always divide by 100 for display.
  • Test vs live keys: sk_test_ prefix for sandbox, sk_live_ for production. Same API, different data.
  • Transfer recipients: Must create a transfer recipient before initiating a transfer. Recipients are reusable.
  • Currency codes: ISO 4217 (NGN, USD, GHS, ZAR, KES, XOF). Not all currencies available in all countries.

Tools discovered (13)

  • Paystack Create Refund

    Create a refund for a Paystack transaction. Pass the transaction reference or ID from list_transactions. Omit amount for a full refund, or specify amount in subunits for a partial refund. Only successful transactions can be refunded.

  • Paystack Create Transaction

    Initialize a new Paystack transaction. Returns authorization_url (payment link to send to customer), access_code, and reference. This does NOT charge the customer — they must visit the authorization_url to complete payment. Amount is in subunits (kobo): 5000 = NGN 50.

  • Paystack Create Transfer

    Initiate a transfer (payout) from your Paystack balance to a recipient. Requires amount in subunits and a recipient_code (RCP_xxx) from create_transfer_recipient. Source is always your Paystack balance. Returns transfer_code and status.

  • Paystack Create Transfer Recipient

    Create a transfer recipient for payouts. Requires recipient type (nuban/ghipss/mobile_money/basa), name, account_number, and bank_code (from Paystack's bank list). Returns a recipient_code needed to initiate transfers via create_transfer.

  • Paystack List Customers

    List customers on your Paystack account. Returns email, customer_code, first_name, last_name, phone, metadata, and risk_action for each customer. Use to find a customer before looking up their transactions or subscriptions.

  • Paystack List Disputes

    List payment disputes (chargebacks) on your Paystack account. Returns dispute ID, status (awaiting-merchant-feedback, awaiting-bank-feedback, pending, resolved), amount, currency, transaction reference, and resolution details. Use to monitor chargebacks and identify transactions needing attention.

  • Paystack List Invoices

    List payment requests (invoices) on your Paystack account. Returns request_code, amount (in subunits), currency, status (pending/paid), customer email, description, and offline_reference. Use to track outstanding invoices and follow up on unpaid requests.

  • Paystack List Refunds

    List refunds processed on your Paystack account. Returns refund ID, amount (in subunits — divide by 100 for display), currency, status, transaction reference, and merchant note. Use for accounting reconciliation or tracking customer refund requests.

  • Paystack List Settlements

    List settlements (payouts) from Paystack to your bank account. Returns settlement ID, total_amount, settled_amount, currency, settlement_date, and deductions. Use for financial reconciliation — correlate with transactions and transfers to track fund flow.

  • Paystack List Subscriptions

    List subscriptions on your Paystack account. Returns subscription_code, status (active, non-renewing, attention, completed, cancelled), plan details, customer email, next_payment_date, and email_token. Use to monitor recurring billing and identify subscriptions needing attention.

  • Paystack List Transactions

    List transactions on your Paystack account. Returns transaction ID, reference, amount (in subunits — divide by 100 for display), currency, status (success/abandoned/failed), channel (card/bank/ussd/mobile_money), customer email, paid_at timestamp, and authorization details. The primary tool for reviewing payment activity and sales volume.

  • Paystack List Transfers

    List transfers (payouts) initiated from your Paystack balance. Returns transfer_code, amount (in subunits), currency, status (success/pending/failed/reversed), recipient details, reason, and created_at. Use to audit outbound payments and reconcile with settlements.

  • Paystack Upsert Customer

    Create or update a Paystack customer. To create: provide email (required), first_name, last_name, phone, metadata. To update: provide customer_code (CUS_xxx from list_customers) plus fields to change. Returns the customer object with customer_code for use in transactions and subscriptions.

Frequently Asked Questions

What is the Paystack MCP server?

Paystack is a payment processing platform that enables businesses to accept online and offline payments in Africa. It facilitates secure transactions, invoicing, and financial tracking for merchants. It provides 13 tools that AI agents can use through the Model Context Protocol (MCP).

How do I connect Paystack to my AI agent?

Add the MCPBundles server URL to your MCP client configuration (Claude Desktop, Cursor, VS Code, etc.). The URL format is: https://mcp.mcpbundles.com/bundle/paystack. Authentication is handled automatically.

How many tools does Paystack provide?

Paystack provides 13 tools that can be called by AI agents, along with a SKILL.md that gives your AI agent domain knowledge about when and how to use them.

What authentication does Paystack require?

Paystack uses API Key. Paystack requires credentials. Connect via MCPBundles and authentication is handled automatically.

Setup Instructions

Connect Paystack to any MCP client in minutes

Ready to use Paystack?

Sign in to connect your credentials and start running tools from the chat.