A Paystack MCP that tells you when it is about to move real money
163 nodes across transactions, charges, subscriptions and plans, transfers and recipients, refunds, disputes, splits and subaccounts, payment requests, dedicated virtual accounts, terminals, storefronts and settlements. One node per operation in Paystack's own OpenAPI document, with no generic catch-all. Seventeen of them move real funds on a live key, every one is marked destructive, and each says on itself whether a retry is safe. Paystack ships no Idempotency-Key header, so that last part is not a formality.
What the Paystack MCP connector does
The Paystack connector for Mattering Automations is 163 nodes on Paystack's API, built from the OpenAPI description Paystack publishes itself. Every one of the 163 operations in that document is a node here: 73 that read and 90 that act. Transactions, charges and the interactive PIN, OTP, phone, birthday and address steps that finish a bank debit. Plans, subscriptions and the update link that recovers an expired card. Transfers, transfer recipients, bulk transfers and the one time password flow that gates them. Refunds, disputes and dispute evidence. Splits, subaccounts, payment requests, products, pages, storefronts and orders. Dedicated virtual accounts, physical and virtual terminals, direct debit mandates, Apple Pay domains, settlements, balance and the balance ledger. There is no catch-all passthrough node, on purpose, because a generic call-any-path node on a payments API is exactly the shape whose blast radius nobody can read off a canvas.
Every capability is a node on the Automations canvas, and every node speaks MCP, the open protocol for connecting AI assistants to tools. Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. The same nodes are also steps in a scheduled workflow, which is the part an assistant on its own cannot do: a payout run that assembles itself at 6am with nobody present, chained to a datatable, a spreadsheet and an approval step.
Read this before you build anything. This connector moves real money, and 17 nodes do it in a way nothing here can undo. Paystack: Charge Authorization and Paystack: Partial Debit debit a saved card. Paystack: Create Charge debits a card, bank account, USSD prompt, mobile money wallet or EFT. Paystack: Initiate Bulk Charge debits many saved authorizations at once. Paystack: Initiate Transfer and Paystack: Initiate Bulk Transfer send funds out of your balance to real bank accounts. Paystack: Create Refund, Paystack: Retry Refund and Paystack: Resolve Dispute return money to customers. Paystack: Create Subscription starts a recurring charge schedule and Paystack: Enable Subscription restarts one. All 17 carry a money-moving flag and are classed destructive, and each one says in its own description that the funds are real and that this API has no recall endpoint.
The sharp edge underneath that is retries, and it is the single most important thing on this page. There is no Idempotency-Key header anywhere on the Paystack API. Searching the whole published specification for idempotency returns exactly one hit: the reference field on a transfer, documented as a lowercase alphanumeric string of at least 16 characters. So transfers are safely retryable, but only when the retry sends the same reference, and a retry that mints a fresh one pays the person twice. Charges, partial debits, bulk charges and refunds are not safely retryable at all: a transaction reference is a uniqueness constraint rather than a documented idempotency key, so a duplicate is rejected instead of answered with the original result. When a call times out and you do not know the outcome, the correct move is to read it back with Paystack: Verify Transaction, Paystack: Check Pending Charge or Paystack: Verify Transfer before touching anything. Every affected node says so on itself, the connector validates a transfer reference against Paystack's documented rule before the request leaves, and it deliberately refuses to generate one for you, because a generated reference is fresh on every retry and that turns one payout into two.
Money is in minor units everywhere, in requests and in responses. Paystack's own wording is that the amount is in kobo for NGN, pesewas for GHS and cents for ZAR, and KES and USD are cents too. NGN 5,000.00 is 500000 and GHS 25.50 is 2550. Every amount field in the catalog repeats that on itself, including the ones where the number looks like an ordinary catalogue price on a product, a page or a plan, and including the share field on a split, where the same number means 20 percent on a percentage split and 20 kobo on a flat one. A factor-of-100 slip is the most expensive mistake available on this API and there is no confirmation step to catch it.
The response envelope has a trap in it that this connector closes. Paystack answers with a status field, a message and a data object, and status is a JSON boolean saying whether the operation succeeded rather than the HTTP status code. The two disagree in both directions, so a perfectly ordinary HTTP 200 can carry a false status with the real reason in the message. A workflow that only checks the HTTP code reports a failed charge as a success. This connector reads both signals and marks a node failed when either one says it failed, quoting Paystack's own message back, so a failed charge cannot propagate down a workflow as a success.
Paystack ships an official MCP server, and it is worth knowing about rather than working around. The @paystack/mcp-server package on npm is first-party, maintained from Paystack addresses, and it is a generic bridge over the same OpenAPI document this connector was built from. It exposes two tools, one that looks up an operation and one that makes a request, it is marked public preview, and it validates at startup that the key is a test key, rejecting live keys outright. That makes the two things complementary rather than competing. Two generic tools against 163 named operations is a different product: an agent choosing between named nodes rather than composing a path string, per-field help that says minor units and which identifier a path wants, pickers on 142 fields so ids are chosen rather than pasted, destructive and money-moving flags a canvas can read, reference validation before a transfer leaves, and boolean-status reconciliation a generic passthrough cannot do because it does not know the vendor's envelope. Live keys work here.
Two things about Paystack itself belong up front rather than after you have built something. Merchant signup is limited to businesses registered in Nigeria, Ghana, South Africa and Kenya, with a private beta in Cote d'Ivoire and Egypt, so if your business is registered elsewhere you may not be able to open an account at all. And test mode is a genuine free sandbox that needs no verification, while going live needs your compliance documents submitted and approved by Paystack. Test and live share one host and one set of paths, so the key prefix is the only thing standing between a workflow and real funds. The connection test reports which ledger the stored key addresses, for exactly that reason.
One connection, three surfaces
- Visual automations. Drag Paystack nodes onto the canvas and wire them to triggers, conditions, and other apps.
- AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
- The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.
Every Paystack node, ready to drop on the canvas
163 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.
Read and query nodes 73
Paystack: Balance Ledger
List every movement in and out of the balance, with the running balance after each. This is the reconciliation view: each row carries a difference, which is the amount that moved, and a balance, which is the total afterwards. Both are in minor units and they behave completely differently when aggregated, which the incremental declaration on this node states.
Paystack: Check Pending Charge
Check whether a pending charge has settled into a final state. Paystack's own instruction is to wait at least 10 seconds before the first check and not to poll in a tight loop. Use this after a charge returned pending, or after any Charge call failed and the outcome is unknown. Reading is always the safe move on this API; retrying the charge is not.
Paystack: Check Slug Availability
Check whether a payment page slug is free before creating the page. Slugs are global across Paystack, not per integration, so an obvious one is usually taken.
Paystack: Fetch Balance
Get the available balance on the integration, one row per currency, in minor units. Read this before a payout run: a bulk transfer larger than the balance fails partway through rather than being rejected up front. It takes no parameters.
Paystack: Fetch Bank Providers
List the banks that can issue a dedicated virtual account for this business. The list is per business rather than global, so read it instead of hardcoding a provider slug. It takes no parameters at all. This is the source for the provider pickers on the dedicated account nodes.
Paystack: Fetch Bulk Charge Batch
Get one bulk charge batch and its progress. total_charges and pending_charges together tell you how far through the batch Paystack is, which is the cheapest way to decide whether a workflow should keep waiting.
Paystack: Fetch Customer
Get one customer by their CUSTOMER CODE or email address, with their saved authorizations, subscriptions and transaction history. Note that this endpoint takes the code while the direct debit endpoints on the same resource take the numeric id.
Paystack: Fetch Dedicated Account
Get one dedicated virtual account with its bank, its number and the customer it is assigned to.
Paystack: Fetch Dispute
Get one dispute with the full transaction behind it, the message history and the deadline. Read this before answering a chargeback: the category and the customer's own messages say what the bank actually wants evidence of.
Paystack: Fetch Dispute Upload URL
Get a signed URL for uploading evidence on a dispute, plus the fileName to quote afterwards. The signed URL grants upload rights to whoever holds it, so it is deliberately not redacted (that would break the only way to attach evidence) and should be treated as sensitive: use it in the next step of the workflow rather than logging or forwarding it. Upload the file with an HTTP node, then call Paystack: Update Dispute with the fileName.
Paystack: Fetch Mandate Authorizations
List one customer's direct debit mandates and their states. Read this before charging a mandate: a revoked or pending mandate cannot be debited, and the numeric authorization id here is what the activation charge node wants. Takes the customer's numeric id and offers no paging parameters.
Paystack: Fetch Order
Get one order by its numeric id, with its items, its buyer and its shipping details.
Paystack: Fetch Page
Get one hosted payment page by its numeric id, including its slug, its custom fields and any products attached to it.
Paystack: Fetch Payment Request
Get one invoice by its numeric id, with its line items, its customer and whether it has been paid.
Paystack: Fetch Payment Session Timeout
Read how long a customer has to complete a payment before the checkout session expires, in seconds. This is an integration wide setting and takes no parameters.
Paystack: Fetch Plan
Get one plan by its code, with its amount, interval and the subscriptions attached to it.
Paystack: Fetch Product
Get one product by its numeric id, including its price, stock and whether it is still in stock.
Paystack: Fetch Product Orders
List every order that includes a given product. This endpoint takes no paging parameters at all, so it returns whatever Paystack decides to return for that product.
Paystack: Fetch Refund
Get one refund by its numeric id, with its status, the amount and the transaction it belongs to.
Paystack: Fetch Settlement Transactions
List the transactions that made up one settlement, which is how a single payout into the bank account is reconciled back to the individual payments behind it. Takes no paging parameters.
Paystack: Fetch Split
Get one split configuration with its member subaccounts and their shares. Takes the split's NUMERIC id, not the SPL_ code, which is a difference worth watching: the code is what goes on a transaction and the id is what addresses the split itself.
Paystack: Fetch Storefront
Get one storefront by its numeric id, with its slug, status and public URL.
Paystack: Fetch Storefront Orders
List the orders placed through one storefront. This endpoint takes no paging parameters at all, so a busy shop returns whatever Paystack decides to return in one response.
Paystack: Fetch Subaccount
Get one subaccount by its code, including the settlement bank and whether Paystack has verified the account.
Paystack: Fetch Subscription
Get one subscription with its plan, its customer, its next payment date and its invoice history.
Paystack: Fetch Terminal
Get one Terminal by its id, with its serial number, name, address and status.
Paystack: Fetch Terminal Event Status
Check whether an event you sent to a Terminal was delivered and acted on. Use it after Paystack: Send Terminal Event, since sending only queues the instruction.
Paystack: Fetch Terminal Status
Check whether a Terminal is online and available before sending it an event. Online means Paystack can reach it; available means it is not mid transaction.
Paystack: Fetch Transaction
Get one transaction by its NUMERIC id. If what you hold is your own reference string rather than an id, use Paystack: Verify Transaction instead. This endpoint returns the same record with the customer, the authorization and the fee breakdown attached.
Paystack: Fetch Transaction Timeline
Get the step by step log of one transaction, from the moment the customer opened the checkout to the final outcome: which channel was chosen, how long each step took, which attempts failed and what the gateway said. This is the node to reach for when a customer says the payment did not work and the transaction record alone does not explain why.
Paystack: Fetch Transfer
Get one transfer by its TRANSFER CODE, with the recipient, the fee charged and the current status. Note the pairing across this resource: fetch takes the code while verify takes your own reference, and they are different values.
Paystack: Fetch Transfer Recipient
Get one payout destination by its recipient code, including the account number and the name the bank returned. Worth reading before a large transfer, to confirm the destination is still what you think it is.
Paystack: Fetch Virtual Terminal
Get one Virtual Terminal by its code, with its destinations and whether it is still active.
Paystack: Generate Subscription Update Link
Get a link the customer can open to change the card their subscription bills. The link is sensitive: anyone holding it can manage that subscription's payment method, so send it to the customer rather than logging it or posting it into a shared channel.
Paystack: List Apple Pay Domains
List the domains registered for Apple Pay on this integration. An empty array means none have been added, which is a normal answer rather than an error. This endpoint offers cursor paging only: there is no page number and no page size parameter at all.
Paystack: List Banks
List the banks and mobile money providers Paystack supports, with the CODE each one is addressed by. Bank codes differ per country and are not SWIFT codes, so filter by country and read the codes rather than assuming them. This is the source for every bank code picker in this connector.
Paystack: List Bulk Charge Batches
List the bulk charge batches on the integration, each with its batch code and its progress counters. Use the batch code to read the individual charges or to pause the run.
Paystack: List Charges in a Batch
List the individual charges inside one bulk batch, with the outcome of each. Filter by status to pull just the failures, which is the usual reason to call this: a batch reports complete whether every charge succeeded or every one of them failed.
Paystack: List Countries
List the countries Paystack supports, with their currencies and the integration types available in each. Worth reading rather than assuming: merchant signup is limited to Nigeria, Ghana, South Africa and Kenya, with more in beta, and this endpoint is the live answer. It takes no parameters and is the source for the country pickers in this connector.
Paystack: List Customers
List the customers on the integration. This is the source for every customer picker in this connector. Two oddities worth knowing: it uses the camelCase page size while offering cursor paging as well, and Paystack's spec types both paging parameters as STRINGS here while typing them as integers elsewhere. The connector sends whatever you set. Rows carry real names, emails and phone numbers.
Paystack: List Dedicated Accounts
List the dedicated virtual accounts on the integration and who each is assigned to. Account numbers are real bank details belonging to your customers, so treat the output accordingly.
Paystack: List Disputes
List the chargebacks customers have filed, with the disputed transaction and the deadline for each. Filter on awaiting-merchant-feedback to find the ones that need an answer: the dueAt field is a real deadline, and a dispute that passes it without evidence is normally decided against the merchant.
Paystack: List Mandate Authorizations
List every direct debit mandate on the integration, filtered by state. This endpoint has a pagination shape of its own, used nowhere else in the API: a bare cursor string plus per_page, with no page number and no use cursor flag. Follow the cursor returned in meta to walk it.
Paystack: List Orders
List the orders created on the integration, with their buyers and statuses.
Paystack: List Pages
List the hosted payment pages on the integration, with their slugs and whether each is active.
Paystack: List Payment Requests
List the invoices issued on the integration, filtered by customer, status, currency or date. Archived requests are not returned, which is what archiving is for. This is the source for the payment request pickers in this connector.
Paystack: List Plans
List the recurring plans on the integration. This is the source for every plan picker in this connector.
Paystack: List Products
List the products on the integration, with stock levels and how many of each have sold. This is the source for the product pickers in this connector.
Paystack: List Refunds
List the refunds issued on the integration, with the transaction behind each and its current status. Watch for the needs-attention status, which means the refund could not be delivered and needs bank details through Paystack: Retry Refund.
Paystack: List Settlements
List the payouts Paystack has made to your own settlement bank account. Worth knowing before building a report on this: the OpenAPI specification declares only page and perPage on this endpoint, with no date range at all, so unlike transactions and transfers it cannot be windowed by date through the documented parameters. Use the escape hatch below if Paystack accepts date filters it has not documented, and page back through the list otherwise.
Paystack: List Splits
List the transaction splits on the integration. Note the paging spelling: this is one of the six endpoints using per_page with an underscore, and the connector maps it for you.
Paystack: List States (AVS)
List the states Paystack accepts for address verification in a country. Use it to fill the state field on Paystack: Submit Address, because a state name Paystack does not recognise fails the verification step rather than being approximated.
Paystack: List Storefront Products
List the products currently in one storefront. No paging parameters are offered on this endpoint.
Paystack: List Storefronts
List the storefronts on the integration. This is the source for the storefront pickers in this connector.
Paystack: List Subaccounts
List the subaccounts on the integration, with their settlement bank details and percentage share. This is the source for every subaccount picker in this connector.
Paystack: List Subscriptions
List subscriptions, optionally filtered to one plan or one customer. Each row carries the subscription code and the email token, which are the two values the disable and enable nodes need together.
Paystack: List Terminals
List the physical Terminals linked to the integration. This list is CURSOR ONLY: it offers next and previous and per_page and has no page parameter at all, unlike almost every other list on this API, so walk it by following the next cursor. It is the source for the Terminal pickers in this connector.
Paystack: List Transaction Disputes
List every dispute filed against one transaction. Use it when a customer queries a payment and you need to know whether a chargeback is already running before issuing a refund, since doing both means paying twice.
Paystack: List Transactions
List the transactions on the integration, filtered by date, status, channel, terminal, customer, subaccount or split. This is the main reporting list and the source for the transaction pickers in this connector. Two things to know about paging here. It spells the page size per_page with an underscore, unlike most Paystack lists, and the connector maps that for you. And it is one of the six endpoints offering cursor paging: for a full sweep, turn cursor paging on and follow the next cursor, because an offset walk over a list that is still growing skips and repeats rows.
Paystack: List Transfer Recipients
List the payout destinations registered on the integration, with the bank account behind each. This is the source for every recipient picker in this connector. It is one of the six endpoints spelling the page size per_page with an underscore, and one of the six offering cursor paging. Rows carry real bank account numbers, so keep the output out of shared logs.
Paystack: List Transfers
List the transfers made from the integration, filtered by date, recipient or status. Like the transaction list, this endpoint spells the page size per_page with an underscore and offers cursor paging, both of which the connector handles for you. Check for the reversed and failed statuses when reconciling: a transfer that left the balance is not the same as one that arrived.
Paystack: List Virtual Terminals
List the Virtual Terminals on the integration with their codes and destinations. This is the source for the Virtual Terminal pickers in this connector.
Paystack: Payment Request Totals
Get the totals of pending and successful invoices, by currency. It takes no parameters at all, so it always describes the whole integration rather than a window. Amounts are in minor units.
Paystack: Requery Dedicated Account
Ask Paystack to re-check a dedicated account for transfers it may not have picked up yet. Use this when a customer says they sent money and no transaction appeared. The response only confirms the requery was accepted; the transaction itself arrives by webhook if there is one to find.
Paystack: Resolve Account Number
Look up the name on a bank account before sending money to it. Run this before creating a transfer recipient or retrying a refund, and check the name that comes back is the person you mean: this is the last cheap moment to catch a mistyped account number, because a completed transfer cannot be recalled through this API.
Paystack: Resolve Card BIN
Look up what a card's first six digits say about it: the issuing bank, the country, the brand and whether it is a debit or credit card. Used for routing decisions and for showing the right card art. The first six digits are not sensitive on their own, but they come from a card number that is.
Paystack: Transaction Totals
Get the total transaction count and volume for a date window, broken down by currency, plus the pending transfer totals. One aggregate for the whole window rather than a row per day, so it answers how much came in without paging the transaction list. Volumes are in minor units.
Paystack: Validate Order
Validate a pay for me order, where one person creates the order and another pays for it. Note that this endpoint takes the order CODE while its siblings take the numeric id, which is the same inconsistency that runs through this API.
Paystack: Verify Authorization
Check whether the customer completed an authorization request. This is the node that tells you a mandate is actually usable, rather than the redirect.
Paystack: Verify Payment Request
Check whether an invoice has been paid. An archived request cannot be verified, which is one reason to archive only what is genuinely finished.
Paystack: Verify Storefront Slug
Check whether a storefront slug is available before creating the shop. Slugs are global, so check before building anything around a name.
Paystack: Verify Transaction
Confirm what actually happened to a transaction, by your own reference. This is the node that decides whether to fulfil an order. Check TWO things in the response and not just one: data.status must be the string success, AND data.amount and data.currency must match what you expected to charge. Amounts are in minor units. Verifying is also the correct way to resolve a charge whose outcome you do not know after a timeout, because retrying the charge is not safe.
Paystack: Verify Transfer
Check the outcome of a transfer using YOUR OWN reference. This is the node to run when a transfer call timed out and you do not know whether the money went: read the outcome here before deciding anything, and if you do retry, retry with the same reference.
Action nodes 90
Paystack: Add Dispute Evidence
Submit the written evidence for a dispute: who the customer was, what they bought and where it was delivered. This is what the bank reads when deciding a chargeback. It contains a real person's contact details and address, so send it once and do not copy it into logs or datatables.
Paystack: Add Products to Page
Attach products to a payment page so buyers can pick from them. This only works on a page created with the product type; adding products to any other kind of page is rejected.
Paystack: Add Products to Storefront
Put existing products into a storefront so buyers can see them. Create the products first with Paystack: Create Product.
Paystack: Add Split Code to Virtual Terminal
Attach a split to a Virtual Terminal so every payment it takes is divided between the main account and the split's subaccounts. This changes where future money goes, so check the split's members before attaching it.
Paystack: Add Subaccount to Split
Add a subaccount to a split, or change the share of one already in it. This same node does both: sending a subaccount that is already a member updates its share rather than failing. Future transactions using this split code are divided the new way.
Paystack: Archive Payment Request
Archive an invoice so it stops appearing in listings. This is filed as destructive because the API offers no unarchive endpoint: an archived request cannot be verified and is no longer returned by Paystack: List Payment Requests, so from the connector's point of view it is gone. Reversing it means the Paystack dashboard.
Paystack: Assign Dedicated Account
Create the customer, validate them and issue a dedicated account in one call, which is the shortcut for onboarding someone who does not exist on the integration yet. It takes identity documents: a BVN in Nigeria plus a bank account to match it against. Those are sensitive personal identifiers, so pass them straight through and do not persist them in workflow variables, logs or datatables.
Paystack: Assign Destination to Virtual Terminal
Add WhatsApp numbers that get notified when this Virtual Terminal takes a payment. Adding a number means a real person starts receiving payment notifications, so confirm the number belongs to whoever should see them.
Paystack: Bulk Create Transfer Recipients
Register many payout destinations at once. The response separates successes from errors, so read both halves rather than assuming the whole batch landed. Duplicate account numbers return the existing recipients instead of creating new ones. Verify the account numbers before sending: a bad one here becomes a recipient code that later gets paid.
Paystack: Charge Authorization
Charge a card or account the customer has already authorized, with no further action from them. This is how recurring billing, saved card checkout and top ups work. MOVES REAL MONEY on a live key (sk_live_). This cannot be undone through this connector. A test key (sk_test_) runs the same call against Paystack's sandbox and touches no real funds. NOT SAFELY RETRYABLE. Paystack has no Idempotency-Key header, and this endpoint documents no idempotency mechanism, so a retry after a timeout can charge twice. If a call times out, read the outcome back (verify by reference, or list and match) before retrying. Only an authorization whose reusable flag is true can be charged this way, and the email must be the one the authorization was created for.
Paystack: Commission Terminal
Link a physical device to this integration by its serial number, so payments taken on it land here. Reversible with Paystack: Decommission Terminal.
Paystack: Create Charge
Charge a customer directly on a channel you choose, without the hosted checkout: card, bank account, USSD, mobile money or EFT. MOVES REAL MONEY on a live key (sk_live_). This cannot be undone through this connector. A test key (sk_test_) runs the same call against Paystack's sandbox and touches no real funds. NOT SAFELY RETRYABLE. Paystack has no Idempotency-Key header, and this endpoint documents no idempotency mechanism, so a retry after a timeout can charge twice. If a call times out, read the outcome back (verify by reference, or list and match) before retrying. Expect this call to return a PENDING state rather than a final one: banks routinely demand a PIN, an OTP, a phone number, a birthday or an address next, and the response status tells you which of the Paystack Submit nodes to call with the same reference. Building this flow means handling every one of those branches; if that is more than the workflow needs, use Initialize Transaction and let Paystack's own checkout page handle them.
Paystack: Create Customer
Create a customer record and get back a customer code. Email is the key: a transaction for an unknown email creates the customer anyway, so this node mostly exists to attach a name and phone before the first payment. Creating one with an email that already exists returns the existing record rather than making a duplicate.
Paystack: Create Dedicated Account
Issue a permanent bank account number to an existing customer, so anything they transfer into it lands on your integration already matched to them. The customer must exist first and, in Nigeria, must be validated before an account can be issued. Dedicated accounts are a Paystack feature that has to be enabled on the business, and availability is limited to Nigeria and Ghana.
Paystack: Create Order
Create an order for a set of products, with the buyer's details and a shipping address. Creating the order does not take payment; it produces an order the buyer then pays for. Item amounts are in minor units.
Paystack: Create Page
Create a hosted payment page with its own public URL, so money can be collected without any website of your own. Set the type to decide what the page sells: a one off payment, a subscription to a plan, a product, or a plan signup. Check the slug is free first with Paystack: Check Slug Availability, because the slug is the public URL.
Paystack: Create Payment Request
Issue an invoice to a customer and get back a request code they can pay. This takes no money by itself, but with send notification on it emails a real customer, so a workflow that fires twice sends two invoices. Create it as a draft first if anything needs checking before the customer sees it.
Paystack: Create Plan
Define a recurring billing plan: an amount, an interval and a name. Creating a plan charges nobody. Money starts moving when a customer is subscribed to it, either through Paystack: Create Subscription or by passing the plan code into a checkout.
Paystack: Create Product
Create a product that can be sold through a payment page or a storefront. The price is in minor units like every other amount on this API, which is the mistake to watch for here because a price reads like a normal number in a product catalogue.
Paystack: Create Refund
Return money to a customer for a completed transaction. MOVES REAL MONEY on a live key (sk_live_). This cannot be undone through this connector. A test key (sk_test_) runs the same call against Paystack's sandbox and touches no real funds. A refund cannot be cancelled or reversed through this API once Paystack has accepted it. NOT SAFELY RETRYABLE. Paystack has no Idempotency-Key header, and this endpoint documents no idempotency mechanism, so a retry after a timeout can charge twice. If a call times out, read the outcome back (verify by reference, or list and match) before retrying. Two important details. Leaving the amount blank refunds the FULL transaction, so a workflow that forgets to set it refunds everything. And check for an open dispute on the transaction first with Paystack: List Transaction Disputes, because refunding a payment that is also being charged back pays the customer twice.
Paystack: Create Split
Define how one payment is divided between the main account and one or more subaccounts, and get back a split code to attach to transactions. Creating a split moves no money; it decides where money goes on every transaction that later carries the code, so an error here is quiet and repeated.
Paystack: Create Storefront
Create a hosted digital shop with its own URL, holding products and taking orders. The storefront is created unpublished; Paystack: Publish Storefront is the separate step that makes it publicly reachable. Check the slug is free first.
Paystack: Create Subaccount
Register a vendor, partner or seller who should receive a share of payments. A subaccount is a real bank account Paystack will settle money into, so the account number and bank code have to be right: Paystack: Resolve Account Number confirms the name on an account before you create the subaccount around it. Creating one moves no money by itself, but every transaction routed to it afterwards does.
Paystack: Create Subscription
Put a customer on a recurring plan. MOVES REAL MONEY on a live key (sk_live_). This cannot be undone through this connector. A test key (sk_test_) runs the same call against Paystack's sandbox and touches no real funds. This is filed as a money moving action because it starts a schedule of charges against the customer's saved authorization, and every one of those charges is real. Paystack bills the first one immediately unless a start date is set. NOT SAFELY RETRYABLE. Paystack has no Idempotency-Key header, and this endpoint documents no idempotency mechanism, so a retry after a timeout can charge twice. If a call times out, read the outcome back (verify by reference, or list and match) before retrying. Creating the same subscription twice bills the customer twice per period, so check for an existing active subscription before creating one.
Paystack: Create Transfer Recipient
Register a bank account or mobile money wallet that money can be sent to, and get back a recipient code. No money moves here, but this is where a mistake becomes permanent: every later transfer names only the recipient code, so a wrong account number is invisible from that point on. Run Paystack: Resolve Account Number first and check the name that comes back is the person you mean. Sending a duplicate account number returns the EXISTING recipient rather than creating a second one.
Paystack: Create Virtual Terminal
Create a Virtual Terminal, which lets a merchant take bank transfer payments in person by showing a code, with the confirmation arriving on a WhatsApp number. Destinations are those notification numbers and at least one is required. Note that this is one of the few endpoints in the API whose spec declares a JSON request body rather than form encoding.
Paystack: Deactivate Authorization
Revoke a saved authorization so it can no longer be charged. This is filed as destructive because there is no reactivate endpoint: the customer has to authorize again from scratch. Any subscription relying on this authorization stops billing, so check what depends on it before revoking. Doing this when a customer asks to stop paying is the correct use.
Paystack: Deactivate Dedicated Account
Release a dedicated virtual account from its customer. The account number stops accepting transfers, and a customer who has saved it as a payee will find their next transfer fails. There is no reactivate endpoint on this API, so this is one way from the connector: the customer would need a new account issued, with a different number.
Paystack: Deactivate Virtual Terminal
Switch off a Virtual Terminal so it stops accepting payments. The API offers no matching reactivate endpoint, so treat this as one way from the connector's point of view: reversing it means the Paystack dashboard or a new terminal.
Paystack: Decommission Terminal
Unlink a physical device from this integration. The device stops taking payments into this account immediately, so a shop with one terminal stops trading the moment this runs. It can be commissioned again, but not by accident and not without the serial number.
Paystack: Delete Product
Delete a product. There is no undelete endpoint on this API, so this cannot be reversed through the connector. Pages and storefronts that list the product lose it. If the intent is to stop selling something rather than to erase it, set the quantity to zero with Paystack: Update Product instead.
Paystack: Delete Storefront
Delete a storefront permanently. There is no undelete endpoint, so this cannot be reversed through the connector, and the public URL stops working immediately for anyone holding a link. To take a shop offline without erasing it, update it rather than deleting it.
Paystack: Delete Transfer Recipient
Deactivate a payout destination so it can no longer be paid. Paystack's own wording is that this sets the recipient to inactive rather than erasing it, and past transfers are untouched, but there is no reactivate endpoint on this API: bringing it back means creating the recipient again. A scheduled payout naming this code starts failing from the moment it runs.
Paystack: Direct Debit Activation Charge
Trigger the small activation charge that brings an inactive direct debit mandate to life for one customer. MOVES REAL MONEY on a live key (sk_live_). This cannot be undone through this connector. A test key (sk_test_) runs the same call against Paystack's sandbox and touches no real funds. It is a real debit against the customer's bank account, small but real, and it cannot be undone through this connector. NOT SAFELY RETRYABLE. Paystack has no Idempotency-Key header, and this endpoint documents no idempotency mechanism, so a retry after a timeout can charge twice. If a call times out, read the outcome back (verify by reference, or list and match) before retrying.
Paystack: Disable Subscription
Stop a subscription from billing again. It is reversible with Paystack: Enable Subscription and it does not refund anything already charged. This endpoint needs BOTH the subscription code and the email token, which is the trap: the token is a separate field on the subscription record, and sending the code alone fails.
Paystack: Disable Transfer OTP
Begin turning off the one time password requirement on transfers, for the WHOLE integration. This is filed as destructive because it removes a security control rather than because it moves money: with it off, anything holding the secret key can send money out of the balance with no second factor at all, which is exactly the exposure that matters if a key ever leaks. Paystack sends a confirming password to the account owner, and Paystack: Finalize Disabling Transfer OTP completes it. Bulk transfers require this to be off, which is the usual reason people run it.
Paystack: Duplicate Storefront
Copy a storefront into a new one, which is the quick way to start a seasonal shop from last season's. The copy gets its own id and slug and starts unpublished.
Paystack: Enable Subscription
Restart a disabled subscription. Billing resumes, so this returns the customer to a schedule of real charges on a live key. Like disable, it needs BOTH the subscription code and the email token.
Paystack: Enable Transfer OTP
Turn the one time password requirement back on for transfers, so every payout needs a second factor again. This is the restoring half of the pair and takes no parameters. Run it as soon as a bulk payout run is finished.
Paystack: Export Disputes
Build a CSV of disputes for a window and return a short lived download link. Fetch the link promptly with a following HTTP node; the response carries its own expiry.
Paystack: Export Transactions
Ask Paystack to build a CSV of transactions for a window and return a download link. The response carries a path and an expiresAt, so the link is short lived and must be fetched promptly by a following HTTP node or worker. Use this instead of paging the transaction list when the window is large and the destination is a spreadsheet rather than a workflow.
Paystack: Export Transfers
Build a CSV of transfers for a window and return a download link. Useful for reconciling a payout run against your own records without paging the transfer list.
Paystack: Finalize Disabling Transfer OTP
Complete turning off the transfer one time password requirement, using the password Paystack sent the account owner. After this runs, every transfer from this integration goes out on the API key alone. Turn it back on with Paystack: Enable Transfer OTP as soon as the batch that needed it is done.
Paystack: Finalize Payment Request
Turn a draft invoice into a live one the customer can pay. This is the step that makes a draft real, and Paystack notifies the customer as part of it, so finalize only what is ready to be seen.
Paystack: Finalize Transfer
Release a transfer that is waiting on a one time password. MOVES REAL MONEY on a live key (sk_live_). This cannot be undone through this connector. A test key (sk_test_) runs the same call against Paystack's sandbox and touches no real funds. This is the step that actually sends the money for an integration with the transfer OTP requirement switched on, and it cannot be recalled afterwards.
Paystack: Initialize Authorization
Start the process of getting a reusable authorization from a customer, so you can charge them later without them being present. The documented channel is direct_debit. This node creates the request and returns a URL for the customer to approve it; nothing is charged until they do and you call a charge node.
Paystack: Initialize Direct Debit
Start linking a customer's bank account for direct debit, so future charges can be taken from it. This endpoint takes the customer's NUMERIC id, while fetch and update on the same resource take the CUS_ code. The account and address objects carry personal banking data and should be passed through without being stored.
Paystack: Initialize Transaction
Start a checkout and get back a Paystack hosted payment URL for the customer to open. This node itself moves no money: it creates a pending transaction and returns authorization_url, access_code and reference. The customer pays on that page, and you learn the outcome from the charge.success webhook or from Paystack: Verify Transaction. Never treat the browser redirect back to your callback URL as proof of payment; it can be replayed and it can simply fail to happen.
Paystack: Initiate Bulk Charge
Charge many saved authorizations in one batch. Paystack queues the batch and works through it, so the response is a batch code rather than a set of outcomes, and the results arrive by webhook or through Paystack: List Charges in a Batch. MOVES REAL MONEY on a live key (sk_live_). This cannot be undone through this connector. A test key (sk_test_) runs the same call against Paystack's sandbox and touches no real funds. It debits every authorization in the list, so a mistake here is multiplied by the size of the batch. NOT SAFELY RETRYABLE. Paystack has no Idempotency-Key header, and this endpoint documents no idempotency mechanism, so a retry after a timeout can charge twice. If a call times out, read the outcome back (verify by reference, or list and match) before retrying. Re-sending a batch charges everyone in it again.
Paystack: Initiate Bulk Transfer
Send money to many recipients in one request, which is how payroll and vendor payout runs are done. MOVES REAL MONEY on a live key (sk_live_). This cannot be undone through this connector. A test key (sk_test_) runs the same call against Paystack's sandbox and touches no real funds. It pays everyone in the list, so an error here is multiplied by the size of the batch and none of it can be recalled. Paystack requires the transfer OTP requirement to be DISABLED before this endpoint works at all, which means the account has already given up its second factor on payouts. Give every entry its own stable reference so a retry cannot pay anyone twice.
Paystack: Initiate Transfer
Send money out of the Paystack balance to a transfer recipient's bank account or mobile money wallet. MOVES REAL MONEY on a live key (sk_live_). This cannot be undone through this connector. A test key (sk_test_) runs the same call against Paystack's sandbox and touches no real funds. Once a transfer completes there is no recall endpoint on this API: getting it back means asking the person who received it. Transfers are the ONE place Paystack documents idempotency, through the reference below, and that only works if a retry sends the SAME reference. If the account requires a one time password, the transfer is held at status otp until Paystack: Finalize Transfer releases it.
Paystack: Partial Debit
Take what you can from a saved authorization when the full amount may not be there. Paystack debits up to the amount and settles for whatever the account holds, subject to the minimum you set. Built for partial recovery on a failed recurring charge. MOVES REAL MONEY on a live key (sk_live_). This cannot be undone through this connector. A test key (sk_test_) runs the same call against Paystack's sandbox and touches no real funds. NOT SAFELY RETRYABLE. Paystack has no Idempotency-Key header, and this endpoint documents no idempotency mechanism, so a retry after a timeout can charge twice. If a call times out, read the outcome back (verify by reference, or list and match) before retrying.
Paystack: Pause Bulk Charge Batch
Stop Paystack working through a bulk charge batch. Charges already processed are not undone; only the remaining ones are held. Resume with Paystack: Resume Bulk Charge Batch. Note that Paystack implements this as a GET request even though it changes state, so it is not a safe read despite the method.
Paystack: Publish Storefront
Make a storefront publicly reachable at its URL. Anyone with the link can then see the products and buy them, so publish when the shop is actually ready rather than as part of setup.
Paystack: Register Apple Pay Domain
Register one domain or subdomain so Apple Pay can be offered on it. Paystack accepts exactly one domain per call, so a workflow registering several needs a loop. The domain has to serve Apple's verification file before registration succeeds.
Paystack: Remove Split Code from Virtual Terminal
Detach a split from a Virtual Terminal, so its payments stop being divided and settle wholly to the main account. This is one of two endpoints on this API that send a DELETE request WITH a body, which many HTTP clients quietly refuse to do. This connector sends it.
Paystack: Remove Split from Dedicated Account
Stop dividing payments into a dedicated account, so they settle wholly to the main account again. This is the second of the two endpoints on this API that send a DELETE request WITH a body; the connector sends it.
Paystack: Remove Subaccount from Split
Take a subaccount out of a split. The subaccount itself is not deleted and past transactions are untouched, but every future transaction using this split stops paying that vendor, so check the split membership afterwards rather than assuming.
Paystack: Resend Transfer OTP
Send the account owner a new one time password for a transfer that is waiting on one. It sends a real message to a real person, so it is not a safe read, but it moves no money by itself.
Paystack: Resolve Dispute
Close a dispute with a decision. MOVES REAL MONEY on a live key (sk_live_). This cannot be undone through this connector. A test key (sk_test_) runs the same call against Paystack's sandbox and touches no real funds. Accepting a chargeback returns the disputed amount to the customer, and the decision cannot be reopened through this API. Read the dispute and its evidence first, and be certain the refund amount in minor units is the figure you mean.
Paystack: Resume Bulk Charge Batch
Restart a paused bulk charge batch. Paystack picks up the remaining charges and debits them, so this resumes real money movement on a live key. Like pause, Paystack implements it as a GET request that changes state.
Paystack: Retry Refund
Retry a refund that came back needing attention, by supplying the customer's bank account. MOVES REAL MONEY on a live key (sk_live_). This cannot be undone through this connector. A test key (sk_test_) runs the same call against Paystack's sandbox and touches no real funds. This sends the refund to whatever account you provide, so a wrong account number here pays a stranger and there is no recall on this API. Confirm the account with Paystack: Resolve Account Number first, and confirm the name it returns is the customer's.
Paystack: Send Payment Request Notification
Email the customer a reminder about an unpaid invoice. This sends a real email to a real person every time it runs, so a reminder loop with no guard is how a customer gets nine emails in a morning. Check the status first and stop when it is paid.
Paystack: Send Subscription Update Link
Have Paystack email the customer a link for updating their subscription card. This sends a real email to a real person, so it is not a safe read even though it changes no data. Use it when a recurring charge failed because the card expired.
Paystack: Send Terminal Event
Push an instruction to a physical Paystack Terminal: show an invoice, process a transaction or print a receipt. The device has to be online, so check with Paystack: Fetch Terminal Status first rather than sending into the dark. Sending a transaction event asks the device to collect a payment, which then happens in the real world with a real card.
Paystack: Set Customer Risk Action
Allow or deny a customer. Setting deny BLOCKS them from transacting on the integration at all, which is a real consequence for a real person and should not be automated on a thin signal. It is reversible by setting the action back to allow or default, so it is a write rather than a destructive action, but treat an automated blocklist as something a human should be able to see and undo.
Paystack: Split Dedicated Account Transaction
Make every payment into a dedicated account divide between accounts, either through a stored split or straight to one subaccount. This changes where future money settles, so confirm the split membership first.
Paystack: Submit Address
Continue a charge that came back asking for address verification. All four address fields plus the reference are required. The state value must be one Paystack recognises for the country, which Paystack: List States (AVS) returns.
Paystack: Submit Birthday
Continue a charge that came back asking for the customer's date of birth, which some banks use as a verification step. Send it with the same reference. Personal data: this value belongs to the customer's bank verification and should not be stored in the workflow.
Paystack: Submit OTP
Continue a charge that came back asking for a one time password. Send the OTP the customer received, with the same reference. This step commonly completes the debit, so it moves real money on a live key. One time passwords expire quickly, so a workflow that parks this step in a queue will fail on arrival.
Paystack: Submit PIN
Continue a charge that came back asking for the card PIN. Send the PIN with the same reference the charge returned. This step can complete the debit, so it moves real money on a live key. The PIN is customer secret material and must not be logged, stored or carried in a variable beyond this step.
Paystack: Submit Phone
Continue a charge that came back asking for the customer's phone number. Send it with the same reference. This step usually advances the charge to a one time password step rather than completing it, so it is filed as a write rather than a money movement, but it is part of a live payment flow.
Paystack: Trigger Activation Charge
Trigger activation charges for MANY customers at once. MOVES REAL MONEY on a live key (sk_live_). This cannot be undone through this connector. A test key (sk_test_) runs the same call against Paystack's sandbox and touches no real funds. Every customer id in the list gets a real debit against their bank account, so the blast radius is the length of the array. NOT SAFELY RETRYABLE. Paystack has no Idempotency-Key header, and this endpoint documents no idempotency mechanism, so a retry after a timeout can charge twice. If a call times out, read the outcome back (verify by reference, or list and match) before retrying. This is one of the few endpoints in the API whose spec declares a JSON body rather than form encoding.
Paystack: Unassign Destination from Virtual Terminal
Stop notifying one or more numbers when this Virtual Terminal takes a payment. Note that the field is called targets here while the assign node calls it destinations, which is Paystack's naming rather than ours.
Paystack: Unregister Apple Pay Domain
Remove a domain from Apple Pay. Apple Pay stops being offered on that domain immediately, so a live checkout loses a payment method the moment this runs. Re-registering is possible but needs the verification file in place again. This is a DELETE request carrying a body, which some HTTP clients refuse; the connector sends it.
Paystack: Update Customer
Change a customer's name, phone or metadata. The email address cannot be changed here, because it is the key Paystack identifies the customer by.
Paystack: Update Dispute
Set the amount you are willing to refund on a dispute, and attach the evidence file you uploaded. This records a position and does not itself move money; Paystack: Resolve Dispute is the step that does. The amount is in minor units.
Paystack: Update Page
Change a payment page's name, description or amount, or switch it off. Setting active to false stops the public URL accepting payments, which is the safe way to retire a page rather than leaving a live link collecting money.
Paystack: Update Payment Request
Change an invoice: its amount, its line items, its due date or who it is addressed to. Changing an invoice the customer has already seen changes what they are being asked to pay, so send a notification or tell them another way.
Paystack: Update Payment Session Timeout
Change how long a checkout session stays open, for the WHOLE integration and every customer on it. A short timeout abandons payments that were nearly finished; a long one holds inventory and stock counts open. Read the current value first, because this is a single global setting with no per transaction override. This is one of the few endpoints whose spec declares a JSON body.
Paystack: Update Plan
Change a plan's name, amount or interval. Read this before changing an amount: existing subscriptions on the plan bill at the new figure from their next charge onward, so a mistyped amount here silently changes what every current subscriber pays. Check who is on the plan first with Paystack: List Subscriptions.
Paystack: Update Product
Change a product's name, description, price or stock. A new price applies to future purchases only and is in minor units.
Paystack: Update Split
Rename a split, activate or deactivate it, or change who pays the Paystack fee. To change the member subaccounts or their shares, use the Add Subaccount and Remove Subaccount nodes instead. Note that the spec types this endpoint's id as a string while the other three split endpoints type it as an integer; the same value works for both.
Paystack: Update Storefront
Change a storefront's name, slug or description. Changing the slug changes the public URL, so any link already shared stops working.
Paystack: Update Subaccount
Change a subaccount's details or its share of transactions. Changing the settlement bank or account number redirects where that vendor's money lands, so treat it with the same care as creating one, and re-verify the account number first. Setting active to false stops future settlements to it.
Paystack: Update Terminal
Rename a Terminal or change the address recorded against it. Useful for keeping reporting readable when devices move between branches.
Paystack: Update Transfer Recipient
Change the name or email on a payout destination. Note what this endpoint does NOT accept: the account number and bank code cannot be changed here, so correcting a wrong account means creating a new recipient and using that code instead.
Paystack: Update Virtual Terminal
Rename a Virtual Terminal. The name is the only field this endpoint accepts; destinations and split codes have their own nodes.
Paystack: Validate Bank Account
Confirm that a bank account belongs to the person or business you think it does, by matching it against an identity document. This is the stronger check that South African payouts use, where Resolve Account Number is the lighter name lookup. It sends identity document numbers, which are sensitive personal data: pass them through and do not store them.
Paystack: Validate Customer
Verify a customer's identity against their bank records, which Nigeria requires before a dedicated virtual account can be issued. This sends government identity numbers and bank details to Paystack: handle them as sensitive personal data, pass them straight through, and do not store them in workflow variables, datatables or logs. Validation is asynchronous and its result arrives by webhook, not in this response.
Connecting Paystack takes one credential
Sign in to your Paystack Dashboard and open Settings, then the API Keys and Webhooks tab. Paystack shows four keys there, a public and a secret key for test mode and the same pair for live mode. Copy the SECRET key, not the public one: public keys start with pk_ and are meant to be embedded in a checkout page, and this connector will tell you plainly if you paste one rather than failing with an unexplained 401. A test secret key starts with sk_test_ and addresses Paystack's sandbox, where none of the money-moving nodes touch real funds. A live secret key starts with sk_live_ and addresses real money on the same host and the same paths. Build on the test key first. Paystack also lets you rotate a secret key from the same screen, choosing when the old one expires, which is the thing to do immediately if a key is ever exposed.
Confirm you can hold a Paystack account. Merchant signup is limited to businesses registered in Nigeria, Ghana, South Africa and Kenya, with a private beta in Cote d'Ivoire and Egypt. This is a Paystack boundary rather than something to debug, and it is worth checking before you design a workflow around it.
Create the Paystack account. It starts in test mode, which Paystack describes as a safe sandbox where you can use Paystack without using real money, and no verification is needed to work there. Going live is a separate step that needs your compliance documents submitted and approved.
In the Paystack Dashboard, open Settings, then API Keys and Webhooks, and copy the test secret key beginning with sk_test_.
In Mattering Automations, open Connectors, click Add Connector and choose Paystack, then click Create new credential and paste the secret key. The key is stored encrypted and never appears in workflow logs.
Click Test Connection. Mattering calls Paystack's balance endpoint, the cheapest authenticated call on the API, which proves the key, the base URL and the header wiring in one request and reports which ledger the key addresses. A 401 means the key is wrong or was rotated. A 403 on a specific resource later means the key is fine and the feature is not enabled on your business, which is normal for dedicated virtual accounts, transfers, terminals and storefronts on a fresh account.
All 163 Paystack nodes appear in the canvas palette. Run Paystack: Fetch Balance first, then Paystack: List Transactions. When you are ready for real money, add a second credential holding the sk_live_ key rather than editing the test one, so a live workflow and a sandbox workflow can never be one careless click apart.
Common uses for the Paystack MCP
A vendor or contractor payout run that cannot pay anyone twice
This is the workflow Paystack is best at and the one most worth getting right. A datatable or a spreadsheet holds who gets paid and how much, in minor units. Paystack: Resolve Account Number checks each account number and returns the account holder's name, which is the last moment a typo is visible to a human. Paystack: Create Transfer Recipient registers each destination and returns a recipient code, or Paystack: Bulk Create Transfer Recipients does the batch, returning successes and errors as two separate halves that both need reading. Paystack: Fetch Balance runs before anything leaves, because a payout run larger than the balance fails partway through rather than being rejected up front. Then Paystack: Initiate Transfer pays each recipient with a reference your workflow computes from the row and the period, so a rerun sends the same reference and Paystack treats it as the same transfer. That reference is the only idempotency Paystack documents anywhere, and it is why this pattern is safe when a blind retry would not be.
Recovering a recurring charge that failed
A subscription charge that fails is revenue that has not gone anywhere yet. Paystack: List Subscriptions and Paystack: Fetch Subscription find the affected customer, and the branch is a judgement call worth encoding once. Where the card is simply out of funds, Paystack: Partial Debit takes what is available above a minimum you set, which is built for exactly this. Where the card has expired, Paystack: Send Subscription Update Link has Paystack email the customer a link to update it, and Paystack: Generate Subscription Update Link returns the link instead if you would rather send it through your own channel. Both nodes reach a real customer, so guard them with a condition rather than letting a retry loop mail somebody five times. Paystack: Charge Authorization is the node that retries the charge itself, and it is one of the not-safely-retryable ones, so read the outcome back with Paystack: Verify Transaction before a second attempt.
Invoicing from a form, a CRM record or a chat message
Paystack: Create Payment Request issues an invoice and returns a request code the customer can pay, so a form submission, a signed proposal or a closed deal in Mattering Sales can produce a real invoice without anybody retyping it. Create it as a draft when something needs checking first, because the send-notification option emails a real person and a workflow that fires twice sends two invoices. Paystack: Send Payment Request Notification sends it when a human has approved it, Paystack: Verify Payment Request checks whether it has been paid, and Paystack: Payment Request Totals gives the outstanding position across all of them. Paystack: Archive Payment Request retires one, and it is permanent, so it is classed accordingly.
Watching disputes before their deadline passes
A chargeback has a clock on it and losing by default is the expensive way to lose. Paystack: List Disputes filtered to awaiting merchant feedback returns the ones that need an answer, each with the disputed transaction and a due date. A scheduled sweep can post them into a Mattering Comms channel or open a Productivity task with the deadline attached, which is a completely read-only way to get value from this connector. Paystack: Fetch Dispute Upload URL and Paystack: Add Dispute Evidence attach the evidence when a person has assembled it. Keep Paystack: Resolve Dispute out of the automatic path: accepting a chargeback returns the disputed amount to the customer and cannot be reopened through this API.
Daily reconciliation that a finance team can actually check
Paystack: Balance Ledger is the reconciliation view, one row per movement with the amount that moved and the running balance afterwards. Both are in minor units and they behave completely differently when you aggregate them, which the node states: amounts sum across a window and balances do not, because a balance is a gauge rather than a flow. Paystack: List Settlements shows what Paystack actually paid into your own bank account and Paystack: Fetch Settlement Transactions breaks one settlement down into the transactions behind it. Paystack: Transaction Totals answers how much came in over a window in one call rather than paging the whole list, and Paystack: Export Transactions returns a short-lived CSV link when the destination is a spreadsheet rather than a workflow. Pushing the daily figures into Mattering Analytics gives you the trend without anybody opening a dashboard.
Fulfilling only what was actually paid for
Paystack: Initialize Transaction starts a checkout and returns a hosted payment URL, an access code and a reference, and it moves no money by itself. The mistake worth designing out is treating the browser redirect back to your callback URL as proof of payment, because it can be replayed and it can simply fail to happen. Paystack: Verify Transaction is the node that decides whether to fulfil, and it needs two checks rather than one: the status must be success, and the amount and currency must match what you meant to charge, in minor units. Only then should the workflow provision the account, ship the order or write the row. Paystack: Fetch Transaction Timeline is what you read afterwards when a customer says they paid and the record disagrees.
Example: A weekly supplier payout run where a person approves the total before any money leaves
Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.
Trigger: a weekly schedule fires. This connector has no trigger nodes, because Paystack's API has no webhook management endpoints, so Paystack workflows run on a schedule or on a generic webhook trigger you point the dashboard at.
A Mattering datatable holds this week's suppliers, their account numbers, bank codes and amounts in minor units. A step converts each amount and asserts it is a whole number, because the difference between 500000 and 5000 is a factor of one hundred and nothing downstream will question it.
Paystack: Resolve Account Number runs on each row and returns the account holder's name from the bank. Any row where the returned name does not match the supplier on file is pulled out of the run rather than paid.
Paystack: Fetch Balance reads the available balance, and the workflow stops if the batch total exceeds it, because a payout run larger than the balance fails partway through rather than being rejected up front.
A Mattering Productivity task is created with the supplier list, the per-row totals and the grand total, and the workflow waits. Nothing has been sent at this point and no node that moves money has run.
On approval, Paystack: Create Transfer Recipient registers any supplier that does not already have a recipient code, and a duplicate account number returns the existing recipient rather than creating a second one.
Paystack: Initiate Transfer pays each recipient with a reference built from the supplier id and the week, at least 16 lowercase alphanumeric characters, so a rerun of the same week sends the same reference and cannot pay anyone twice. The connector checks that reference against Paystack's documented rule before the request leaves.
Paystack: Verify Transfer reads each transfer back on the next run and the results are written to the datatable, so the record of what was paid comes from Paystack rather than from the assumption that the request succeeded.
Paystack MCP questions, answered
What can this connector actually do in Paystack?
163 nodes, one per operation in Paystack's published OpenAPI document, with 73 that read and 90 that act. Reads cover transactions, transaction totals and timelines, charges, customers and their authorizations, plans, subscriptions, transfers, transfer recipients, refunds, disputes and dispute evidence uploads, splits, subaccounts, payment requests and their totals, products, pages, storefronts and orders, dedicated virtual accounts and their providers, terminals and virtual terminals, direct debit mandates, Apple Pay domains, banks, countries, AVS states, balance, the balance ledger and settlements. Writes cover initializing a checkout, charging a saved authorization, partial debits, direct charges and the PIN, OTP, phone, birthday and address steps that complete them, bulk charges, creating and updating customers, plans, subscriptions, splits, subaccounts, payment requests, products, pages, storefronts and orders, creating and paying transfer recipients singly and in bulk, the transfer one time password flow, refunds, dispute updates and resolutions, terminal commissioning and events, and the permanent deletes. There is no generic call-any-endpoint node. Not included: webhook management, because Paystack has no webhook endpoints on its API at all and configures them in the dashboard instead.
Paystack ships its own MCP server. Why use this one?
Both can be useful, and they are not the same kind of thing. The official @paystack/mcp-server package on npm is first-party, maintained from Paystack addresses, and it is a generic bridge over the same OpenAPI document this connector was built from: two tools, one that looks up an operation by id and one that makes a request. It is marked public preview and it validates at startup that your key is a test key, rejecting live keys. That is a reasonable design for exploring the API from an assistant. This connector is 163 named operations instead of two generic ones, which changes what an agent can do reliably: it chooses between named nodes rather than composing a path string, every field carries help that says minor units and which identifier that path wants, 142 fields have pickers so ids are chosen rather than pasted, the 17 money-moving nodes are flagged so a canvas can show it, transfer references are validated before the request leaves, and the boolean status in Paystack's envelope is reconciled against the HTTP code, which a generic passthrough cannot do because it does not know the vendor's envelope. The other differences are about where the thing runs. These nodes are also steps in a scheduled workflow that runs with nobody present, they chain with every other connector in one automation, and the credential lives once in a shared workspace rather than in each person's local config.
Does this work with Claude, ChatGPT, or other AI assistants?
Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and work with Paystack through them. Matter, the assistant built into the platform, uses the same nodes natively. Because the same nodes are canvas steps, a workflow an assistant helps you design can then run on a schedule with nobody watching. Given what this connector can reach, the sensible split is to hand an assistant the 73 read nodes and keep the writes, and above all the 17 that move money, behind a condition or a human approval step.
Is it safe to let an AI agent move money through this?
It is a decision to make deliberately rather than a yes or a no, and the connector is built so the careful version is the easy one. Seventeen nodes move real funds on a live key and every one of them is classed destructive and says so in its own description rather than in a footnote somewhere. Twenty eight nodes in total are destructive, which adds the permanent deletes and the two that turn off the one time password gate on every future transfer for the whole integration. The rest split into 76 safe reads and 59 reversible writes. The practical setup is three things: point agents at a test key, which is a full free sandbox where none of those nodes touch real money, keep the money-moving nodes behind an approval step on the canvas rather than inside an agent's reach, and give a live workflow its own credential so it is never one careless click from a sandbox one. The retry rules matter here too, because an agent that retries on a timeout is doing the exact thing that charges a card twice.
What are Paystack's rate limits?
We do not know, and we are not going to invent a number. Paystack's published OpenAPI document declares no 429 response on any of the 163 operations and no rate-limit headers, and a live unauthenticated call returned none either, so there is no figure here we can cite. What we can tell you is what happens if you meet one. A 429 from Paystack is reported as a failure with an explanation attached saying the limit is undocumented and to slow the workflow down rather than assume a ceiling, and it explicitly tells you not to blind retry a charge or a transfer, because only transfers have an idempotency key. The general shape advice holds regardless: prefer one wide call to many narrow ones, use Paystack: Transaction Totals instead of paging the whole transaction list to get a window's volume, and use Paystack: Export Transactions when the destination is a spreadsheet.
Why are all the amounts so large, and what is a minor unit?
Paystack takes and returns every amount in the smallest unit of the currency. Its own wording is kobo for NGN, pesewas for GHS and cents for ZAR, and KES and USD are cents too. So NGN 5,000.00 is 500000 and GHS 25.50 is 2550. Every amount field in this connector repeats that rule in its own help text, because the config panel is the only place a workflow author will read it and a factor-of-100 slip on this API has no confirmation step behind it. Watch three places especially. Prices on products, pages and plans look like ordinary catalogue numbers and are not. The share field on a split means 20 percent on a percentage split and 20 kobo on a flat one, from the same number. And responses are in minor units too, so a total assembled from the transaction list needs dividing before a human reads it. The currencies Paystack's specification lists are GHS, KES, NGN, ZAR and USD.
Can I use this if my business is not in Nigeria, Ghana, South Africa or Kenya?
Probably not, and the limit is Paystack's rather than the connector's. Paystack states that its services are available only to businesses registered in Nigeria, Ghana, South Africa and Kenya, and it runs a private beta in Cote d'Ivoire and Egypt. If your business is registered outside those countries you may be unable to complete signup and so unable to obtain even a test key. We would rather say that here than have you find it after designing a workflow around it, and we are not going to put a date on wider availability. Nothing about the connector is country-limited: it is one secret key against one host, and it works the moment you have a key.
Can a workflow react to a Paystack event, like a successful payment?
Not through a Paystack node, and the reason is that Paystack has no webhook management endpoints anywhere in its API. Webhooks exist as a Paystack feature but they are configured in the dashboard, so there is nothing for a connector to create or subscribe to and this connector therefore has no trigger nodes. Two patterns cover it. Point your Paystack dashboard webhook URL at Mattering's generic webhook trigger, and the rest of the workflow, including every Paystack node, runs from there. Or run on a schedule and read: Paystack: List Transactions with cursor paging turned on sweeps what is new without skipping or repeating rows the way an offset walk over a growing list does. Either way, confirm a payment with Paystack: Verify Transaction before you act on it, checking both that the status is success and that the amount and currency match what you expected.
Put Paystack to work inside your workspace
Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.
All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Paystack is a product of its respective owner; Mattering is an independent platform.