Resources · Make integration

Paystack Make integrationAutomate Paystack with Make.

Can Paystack payments, refunds and disputes run on their own? The Paystack Make integration gives you 61 modules, with 7 instant triggers among them. It suits finance and ops teams that live in the Paystack dashboard. This guide links your account and walks you through a first scenario.

Try the Paystack integration on MakeSee the 61 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Paystack Make integration automate?

The Paystack Make integration links your Paystack account to Make, a no-code automation tool. You build a scenario, meaning the automation itself, out of modules: each module is one brick, such as a trigger that listens to Paystack or an action that creates a refund. No code, and no API knowledge needed to start.

Chargebacks handled with less scrambling. Watch Disputes wakes the scenario when a dispute is created, reminded or resolved. Get a Dispute pulls the full record, and Add an Evidence attaches your proof, so the case file builds itself around the event.

Subscriptions that get a second chance. When Watch Subscriptions reports a disabled plan, Send an Update Subscription Link can email the customer a link to change the card on it. Enable a Subscription switches the plan back on when the customer returns.

Invoices that leave on cue. An order in your store can call Create an Invoice, then Finalize an Invoice and Send a Notification, so the customer gets the invoice without anyone copying data by hand.

Where no module fits, Make an API Call reaches any endpoint of the Paystack API with the same connection. The documentation also warns that its content is AI-generated from Paystack's own docs, so double-check anything critical with Paystack. If you are weighing tools, the n8n vs Make comparison lays out the criteria, and our Make review covers the editor in depth. Teams that prefer help can talk to our Make agency.

Connect

How do you connect Paystack to Make?

  1. 01

    Copy your Secret Key from Paystack

    In the Paystack Dashboard, open Settings, then the Developers tab, then API Keys and Webhooks. Copy the key labeled Secret Key. You need an active Paystack account for this.

  2. 02

    Add a Paystack module in Make

    Log in to Make, add any Paystack module to your scenario and click Create a connection. A connection is your Paystack account linked to Make once, then reused by every Paystack module. The Connection name field is optional.

  3. 03

    Paste the key and save

    Paste the Secret Key you copied, or follow the instructions Make shows on screen, and save. Make can now read and write in your Paystack account, and every other Paystack module will offer this connection in its list.

First scenario

Your first scenario: verify each successful Paystack payment

GoalWhen a payment succeeds in Paystack, Make verifies the transaction and fetches the customer behind it.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. Search for Paystack and pick Watch Transactions as your first module.

  2. 02

    Link the webhook and your account

    Click Create a webhook, then Create a connection and paste your Secret Key. From now on, Paystack tells Make about each successful transaction as soon as it happens.

  3. 03

    Add Verify a Transaction

    Click the + on the right of the trigger and choose Verify a Transaction. Map the transaction data the trigger received, so Make checks the payment straight with Paystack.

  4. 04

    Fetch the customer

    Add Get a Customer after it and map the customer from the previous bundle (a bundle is one item passed from a module to the next, here one payment). You now hold the payment and the buyer in one run, ready for a CRM or a sheet later on.

  5. 05

    Test with Run once

    Click Run once to execute the scenario one time. Then read the bundles each module received and confirm the data looks right.

  6. 06

    Switch it on

    Turn the scenario on. Each module run counts as one operation, the unit Make bills on your plan, so three modules mean three operations per payment.

Triggers

Which Paystack events can start a scenario?

7 modules start a scenario when something happens in Paystack. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Paystack as soon as it happens.

Paystack1Watch Customer Identifications

Watch Customer Identifications

Instant trigger

In Make“Triggers when a new customer identification event (success or failed) occurs.”

Your scenario starts each time Paystack finishes identifying a customer, and the bundle tells you whether the identification succeeded or failed. One bundle is one event, handed to the next module.

How it fires
instant: Paystack calls Make through a webhook as soon as it happens.
When to use it
onboarding that waits on identity checks, where someone should hear about a failed check without refreshing the dashboard.
Watch out
successes and failures come through the same trigger, so look at the outcome before you act on it.
Paystack2Watch Disputes

Watch Disputes

Instant trigger

In Make“Triggers when a new dispute event (created, reminder or resolved) occurs.”

Get told about chargebacks right away: this trigger hands you each dispute event Paystack records, whether it is a new dispute, a reminder about an open one, or a resolution.

How it fires
instant: Paystack calls Make through a webhook as soon as it happens.
When to use it
when a support or finance person has to gather proof quickly. Chain it with Get a Dispute and Add an Evidence to prepare the case.
Watch out
three kinds of events share this trigger, so a scenario built for new disputes should check the type first.
Paystack3Watch Invoices

Watch Invoices

Instant trigger

In Make“Triggers when a new invoice event (created, updated or failed) occurs.”

Follow the life of your Paystack invoices from Make. Each time an invoice is created, updated or fails, the scenario receives that event as a bundle.

How it fires
instant: Paystack calls Make through a webhook as soon as it happens.
When to use it
a finance team that wants failed invoices flagged in its shared inbox or task tool, so someone calls the client while the order is still fresh.
Watch out
creation, updates and failures all arrive here; keep only the kind your scenario was built for.
Paystack4Watch Payment Requests

Watch Payment Requests

Instant trigger

In Make“Triggers when a new payment request event (pending or successful) occurs.”

Know where each payment request stands without checking Paystack. The trigger passes along every request event, pending or successful, to the modules that follow.

How it fires
instant: Paystack calls Make through a webhook as soon as it happens.
When to use it
a freelancer or small agency that bills through payment requests and wants each paid one logged in a spreadsheet or marked done in a project tool.
Watch out
pending requests trigger it too, so do not treat every bundle as money received.
Paystack5Watch Subscriptions

Watch Subscriptions

Instant trigger

In Make“Triggers when a new subscription event (created or disabled) occurs.”

Keep access in step with billing. This trigger reports when a subscription is created or disabled in Paystack, one bundle per event.

How it fires
instant: Paystack calls Make through a webhook as soon as it happens.
When to use it
a membership site or SaaS that opens an account when a plan starts and closes it when the plan is disabled, with no one updating lists by hand.
Watch out
both events share one trigger; route them apart before granting or removing access.
Paystack6Watch Transactions

Watch Transactions

Instant trigger

In Make“Triggers when transaction was successful.”

Start work the moment money lands. Watch Transactions sends Make each successful transaction, which makes it the natural first module for order fulfillment and receipts.

How it fires
instant: Paystack calls Make through a webhook as soon as it happens.
When to use it
an online shop that should confirm an order, update stock in another app or thank the buyer once the payment clears.
Watch out
the trigger covers successful transactions only, so a failed attempt never starts this scenario.
Paystack7Watch Transfers

Watch Transfers

Instant trigger

In Make“Triggers when a new transfer event (successful, reversed or failed) occurs.”

Track the money you send out. Each transfer event, successful, reversed or failed, reaches your scenario as a bundle you can log or act on.

How it fires
instant: Paystack calls Make through a webhook as soon as it happens.
When to use it
a marketplace paying sellers or a company paying suppliers, where a failed or reversed payout must reach the accountant before the supplier chases it.
Watch out
reversed and failed transfers arrive next to successful ones; sort them before you notify anyone.
Modules

What can each Paystack module do?

Paystack gives you 54 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Paystack1

Add an Evidence

Action

In Make“Adds an evidence for a dispute.”

Build your side of a dispute from Make: this action attaches evidence to an open Paystack dispute, using the details your scenario already gathered.

When to use it
right after Watch Disputes and Get a Dispute, when order data from your shop or delivery tool can back your case.
Watch out
if the proof is a file, pair it with Get an Upload URL, which exists for dispute evidence uploads.
Paystack2

Archive an Invoice

Action

In Make“Archives an invoice.”

Tidy your invoice list without deleting anything. Archive an Invoice moves one Paystack invoice out of the active list so your team stops chasing it.

When to use it
when an order is cancelled in your store or CRM and the matching invoice should no longer appear among open ones.
Watch out
the module acts on one invoice; to archive several, find them first with Search Invoices.
Paystack3

Charge an Authorization

Action

In Make“Charges an authorization.”

Bill a returning customer again without sending them to checkout. This action charges a card authorization Paystack already holds from an earlier payment.

When to use it
usage-based billing or a second installment, when your app records what the customer owes and Make collects it.
Watch out
if you plan to charge right away, skip Check an Authorization first, because that check holds funds and can cause an insufficient funds error.
Paystack4

Check an Authorization

Action

In Make“Checks an authorization. All Mastercard and Visa authorizations can be checked with this endpoint to know if they have funds for the payment you seek. This feature is only available to businesses in Nigeria. Warning! You shouldn't use this endpoint to check a card for sufficient funds if you are going to charge the user immediately. This is because we hold funds when this endpoint is called which can lead to an insufficient funds error.”

Find out whether a saved Mastercard or Visa authorization has enough funds for an amount, before you commit to the charge.

When to use it
ahead of a large order or a delayed charge, when you want a warning instead of a declined payment later.
Watch out
only businesses in Nigeria can use it, and Paystack holds funds during the check, so never run it just before Charge an Authorization.
Paystack5

Create a Customer

Action

In Make“Creates a customer.”

Put a new buyer into Paystack as soon as they show up elsewhere. The action creates the customer record, so later payments, invoices and subscriptions have someone to attach to.

When to use it
a lead signs a quote in your CRM or fills a signup form, and billing should be ready before the first payment.
Watch out
run Search Customers first when the same person might already exist.
Paystack6

Create a Dedicated Account

Action

In Make“Creates a dedicated NUBAN and assigns it to a customer.”

Give a customer an account of their own for paying you. The module creates a dedicated NUBAN account in Paystack and assigns it to that customer.

When to use it
clients who pay by bank transfer, such as a wholesaler whose retailers top up their balance, so each payment arrives already tied to the right person.
Watch out
the customer must exist in Paystack first, so place Create a Customer or Search Customers before it.
Paystack7

Create an Invoice

Action

In Make“Creates an invoice for a payment.”

Turn an order or a quote into a Paystack invoice without retyping a thing. Make maps the customer and the amount from the previous module into a new invoice for that payment.

When to use it
a deal marked won in your CRM, or a booking confirmed in your calendar tool, that should produce the invoice on its own.
Watch out
if the invoice starts as a draft, add Finalize an Invoice before you send it.
Paystack8

Create a Product

Action

In Make“Creates a product.”

Keep your Paystack catalog in line with the one you already manage. This action adds a product to Paystack from data another tool sends into the scenario.

When to use it
a new item added to your shop, spreadsheet or inventory app that should exist in Paystack too, without a second entry by hand.
Watch out
each run creates a new product, so check with Search Products when duplicates are possible.
Paystack9

Create a Refund

Action

In Make“Initiates a refund.”

Send money back from your support process instead of the dashboard. The module starts a refund in Paystack for the transaction you point it to.

When to use it
a return approved in your helpdesk or a cancelled booking, where the refund should follow the decision straight away.
Watch out
money leaves your account, so test on a single transaction with Run once before you switch the scenario on.
Paystack10

Create a Subscription

Action

In Make“Creates a subscription.”

Start recurring billing for a customer from any tool that knows they signed up. The action creates the subscription in Paystack for that customer.

When to use it
a contract signed in your e-signature tool, or a plan chosen in your app, that should begin billing without anyone touching Paystack.
Watch out
Watch Subscriptions will fire for the new subscription too, so keep the two scenarios from feeding each other.
Paystack11

Deactivate a Dedicated Account

Action

In Make“Deactivates a dedicated account.”

Close a customer's dedicated account when the relationship ends. The action switches that dedicated account off in Paystack.

When to use it
a client churns or a retailer leaves your network, and you no longer want transfers landing on the number you gave them.
Watch out
fetch the account with Get a Dedicated Account or Search Dedicated Accounts first, so you deactivate the right one.
Paystack12

Deactivate an Authorization

Action

In Make“Deactivates an authorization when the card needs to be forgotten.”

Make Paystack forget a saved card. Deactivate an Authorization turns off a card authorization when the customer, or your policy, says it should no longer be used.

When to use it
a customer asks your support team to remove their card, or closes their account in your app.
Watch out
this is about the saved card, not the customer; their Paystack record stays, and Update a Customer is the module for their details.
Paystack13

Disable a Subscription

Action

In Make“Disables a subscription.”

Stop a customer's recurring billing from wherever the cancellation happens. The module disables that subscription in Paystack.

When to use it
a cancellation form, a churn tag in your CRM or an unpaid account flagged in your back office should end the plan.
Watch out
Watch Subscriptions reports disabled subscriptions, so a scenario on that trigger will pick up this change too.
Paystack14

Enable a Subscription

Action

In Make“Enables a subscription.”

Bring a paused plan back to life. Enable a Subscription switches a disabled Paystack subscription on again, with no new signup needed.

When to use it
a customer fixes their card after an update link, or a win-back offer is accepted in your CRM, and billing should resume.
Watch out
it only works on an existing subscription; for a brand new plan, use Create a Subscription instead.
Paystack15

Export Disputes

Action

In Make“Exports disputes that are available on your integration.”

Pull the disputes on your Paystack integration in one export instead of opening them one by one.

When to use it
when your finance lead reviews chargebacks with the accountant, or before a meeting with your payments provider, and wants every case in a single file.
Watch out
to act on one case, Get a Dispute gives you its details; this module is for the whole picture.
Paystack16

Finalize an Invoice

Action

In Make“Finalizes a draft invoice.”

Move a draft invoice to its final state so it is ready for the customer. The module takes an invoice created as a draft and finalizes it.

When to use it
after Create an Invoice, once a manager has approved the amount in your approval tool.
Watch out
place it before Send a Notification; a draft is not what you want in a customer's inbox.
Paystack17

Finalize a Transfer

Action

In Make“Finalizes an initiated transfer.”

Complete a payout that is still waiting. Finalize a Transfer takes a transfer you already initiated and pushes it through.

When to use it
a payout that Initiate a Transfer started earlier in the flow, or in another scenario, and that you now want to carry to completion.
Watch out
it works on a transfer that already exists; it does not create one, so Initiate a Transfer always comes first.
Paystack19

Get a Customer

Action

In Make“Fetches a customer.”

Load one customer's Paystack record into the scenario, so the next modules can use their details.

When to use it
after Watch Transactions, when your CRM or email tool needs the buyer's data and the transaction alone does not carry enough.
Watch out
it returns one known customer; when you only have a partial detail, start with Search Customers instead.
Paystack20

Get a Dedicated Account

Action

In Make“Fetches a dedicated account.”

Read the details of one dedicated account, the NUBAN you assigned to a customer, straight from Paystack.

When to use it
when an onboarding email or a client portal needs to show the customer the account they should pay into.
Watch out
you need the account to identify it; if you only know the customer, list accounts with Search Dedicated Accounts first.
Paystack21

Get a Dispute

Action

In Make“Gets more details about a dispute.”

See the full story of a dispute. The module gets more details about one dispute, beyond what the trigger event carried.

When to use it
right after Watch Disputes, to post a complete summary in your team chat or open a ticket with everything the agent needs.
Watch out
to see every dispute tied to one payment, List Transaction Disputes is the better fit.
Paystack22

Get an Invoice

Action

In Make“Gets details of an invoice.”

Pull the details of one Paystack invoice into your scenario, so other tools can show or store them.

When to use it
after Watch Invoices reports a failure, to push the amount and customer into a follow-up task for your finance team.
Watch out
the module reads one invoice; for a list with filters, reach for Search Invoices.
Paystack23

Get an Upload URL

Action

In Make“Gets URL to upload a dispute evidence.”

Obtain an address where you can upload a file as evidence for a dispute. That is its only job, and it is the step people forget.

When to use it
when your proof is a delivery receipt or a signed form stored in a drive, and it must reach Paystack alongside Add an Evidence.
Watch out
on the Free plan, Make handles files up to 5 MB.
Paystack24

Get a Product

Action

In Make“Gets more details of a product.”

Read one product from your Paystack catalog with its details, ready to map into the following modules.

When to use it
before Update a Product, to compare what Paystack has with what your shop or spreadsheet says.
Watch out
this fetches one product you already know; to find it by name or browse the catalog, use Search Products.
Paystack25

Get a Refund

Action

In Make“Gets details of a refund.”

Check where a refund stands. The module gets the details of one refund from Paystack, so you can tell the customer something precise.

When to use it
when a helpdesk ticket asks about money not yet received, and the agent needs the refund details in the ticket.
Watch out
it reads a known refund; to review several, Search Refunds lists them.
Paystack26

Get a Subscription

Action

In Make“Gets details of a subscription.”

Load a single subscription with its details, so a scenario can decide what to do next based on it.

When to use it
after Watch Subscriptions, when your membership tool needs the plan details before it grants or removes access.
Watch out
one known subscription only; for an overview, Search Subscriptions returns several bundles.
Paystack27

Get a Transfer

Action

In Make“Gets details of a transfer.”

Read the details of one transfer you made through Paystack, whatever state it is in.

When to use it
when a supplier asks where their money is and your accounts team wants the transfer details in the ticket or the ledger.
Watch out
to confirm the final status of a transfer, Verify a Transfer is the module made for that.
Paystack28

Initialize a Transaction

Action

In Make“Initializes a transaction.”

Open a payment in Paystack before the customer pays. The action initializes a transaction your scenario can then hand over to the buyer.

When to use it
a quote accepted in your CRM or a booking confirmed in a form, where the customer should receive a way to pay right after.
Watch out
initializing is not collecting; Watch Transactions or Verify a Transaction tells you when the payment really succeeded.
Paystack29

Initiate a Transfer

Action

In Make“Initiates a transfer. Status of transfer object returned will be pending if OTP is disabled. In the event that an OTP is required, status will read OTP.”

Send money out of Paystack from a scenario, for example to a seller, a supplier or a partner.

When to use it
payouts approved in a spreadsheet or an approval tool, so no one retypes amounts into the dashboard.
Watch out
the transfer comes back pending when OTP is disabled, or with the status OTP when an OTP is required, so read the status before the next step.
Paystack30

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reach any part of the Paystack API that the listed modules do not cover, using the connection you already set up.

When to use it
when your process needs an endpoint with no ready module, for example a request your team found in Paystack's API documentation.
Watch out
you describe the request yourself, so keep Paystack's API docs open; Make training covers this module step by step.
Paystack31

Register a Domain

Action

In Make“Registers a top-level domain or subdomain.”

Add a top-level domain or a subdomain to your Paystack integration from a scenario, instead of setting it up by hand.

When to use it
an agency or platform that launches client shops on new domains and wants each new domain registered as part of the launch process.
Watch out
Unregister a Domain does the reverse; keep both steps tied to the same domain list.
Paystack32

Resolve a Card BIN

Action

In Make“Gets more information about a customer's card.”

Learn more about a customer's card from its BIN, before you rely on that card for anything important.

When to use it
a risk check on a new customer, where your team wants card information added to the customer's file before approving a large order.
Watch out
it describes the card, it does not check funds; that is the job of Check an Authorization.
Paystack33

Resolve a Dispute

Action

In Make“Resolves a dispute.”

Close a dispute from your scenario once the decision is made, so nobody has to log in to Paystack for it.

When to use it
when your support lead marks a chargeback as settled in the helpdesk, and Paystack should reflect it.
Watch out
Watch Disputes fires on resolved disputes too, so a scenario on that trigger will see this change.
Paystack34

Resolve an Account Number

Action

In Make“Confirms that an account belongs to the right customer.”

Confirm that a bank account belongs to the right customer before any money moves to it.

When to use it
a seller or supplier gives you bank details through a form, and you want the check done before Initiate a Transfer ever runs.
Watch out
place it early in the flow; catching a wrong account after a payout is far more work.
Paystack35

Send a Notification

Action

In Make“Sends notification of an invoice to your customers.”

Email a Paystack invoice to your customer from the scenario, so it reaches them the moment it is ready.

When to use it
right after Finalize an Invoice, or when a reminder should go out because Watch Invoices reported a failure.
Watch out
sending a draft is rarely what you want; finalize the invoice before this module.
Paystack37

Unregister a Domain

Action

In Make“Unregisters a top-level domain or subdomain previously used for your Apple Pay integration.”

Remove a top-level domain or subdomain you previously used for your Apple Pay integration on Paystack.

When to use it
a client shop closes or moves to a new address, and the old domain should stop being attached to your Apple Pay setup.
Watch out
it only concerns domains registered for Apple Pay, typically through Register a Domain.
Paystack38

Update a Customer

Action

In Make“Updates a customer's information.”

Keep a customer's Paystack record current when their details change somewhere else.

When to use it
a client updates their email or phone in your CRM or account page, and Paystack receipts should follow.
Watch out
you need to know which customer to update, so place Search Customers or Get a Customer before it.
Paystack39

Update an Invoice

Action

In Make“Updates an invoice details.”

Change the details of an existing Paystack invoice without recreating it from scratch.

When to use it
a quote is revised in your CRM after the invoice was created, and the amount or customer detail must match.
Watch out
Watch Invoices fires on updates, so a scenario on that trigger will run again after this change.
Paystack40

Update a Product

Action

In Make“Updates a product details.”

Edit a Paystack product from your own catalog, so the two lists stay in sync.

When to use it
a price or a name changes in your shop or in the spreadsheet your team maintains, and Paystack should carry the same data.
Watch out
find the product first with Search Products or Get a Product; an update needs to know its target.
Paystack41

Validate a Customer

Action

In Make“Validates a customer.”

You get a clear answer on whether a customer passed Paystack's validation, so the scenario only moves forward with people who cleared the check. The result arrives as a bundle, the item handed from one module to the next.

When to use it
right after Create a Customer, when your own process wants a validated customer before opening a dedicated account or sending a first invoice.
Watch out
Watch Customer Identifications reports whether an identification succeeded or failed; it can start a separate scenario that follows up on the failures.
Paystack42

Verify a Transaction

Action

In Make“Verifies a transaction.”

Your scenario gets Paystack's own word on a payment, so an order is marked paid or access is unlocked only once Paystack confirms it. Each check costs one operation, a single run of a module that Make counts on your plan.

When to use it
after Initialize a Transaction, once the buyer has gone through checkout and your shop waits for proof before shipping.
Watch out
Watch Transactions already fires on successful payments; if that trigger starts the scenario, ask whether a second verification still adds anything for your case.
Paystack43

Verify a Transfer

Action

In Make“Verifies the status of a transfer.”

With this module, the scenario reads where a payout stands in Paystack and can branch on that status instead of assuming the money has left.

When to use it
after Initiate a Transfer, before telling a supplier or a partner that their payout is on its way.
Watch out
a transfer that came back pending or with the status OTP is not done yet; wait until it is finalized before you promise the payout.
Paystack44

Verify BVN Match

Action

In Make“Checks if an account number and BVN are linked.”

This check tells you whether an account number and a BVN are linked, giving your onboarding flow a plain yes or no before any money goes to that account.

When to use it
when a new seller or customer hands over bank details and you want that link confirmed before a transfer is created for them.
Watch out
the answer only covers the pair you send; map both values from the same bundle so the account number and the BVN really belong to the same person.
Paystack45

Whitelist / Blacklist a Customer

Action

In Make“Whitelists or blacklists a customer on your integration.”

One module changes how Paystack treats a customer on your integration: trusted on the whitelist, blocked on the blacklist. Both directions live in the same module.

When to use it
when Watch Disputes reports a new dispute and your policy is to block that customer while the case is open, or to restore them once it is resolved.
Watch out
a blacklist entry written by an automation lands on a real customer; click Run once on a test customer before switching the scenario on.
Paystack46

List Transaction Disputes

Search

In Make“Retrieves disputes for a particular transaction.”

You get every dispute tied to one transaction in a single pass, which gives support the full history of a contested charge instead of a single case.

When to use it
when a customer writes in about a payment and the ticket should carry all the disputes linked to it.
Watch out
like any search, it can return zero, one or several bundles; plan the case where no dispute comes back so the rest of the scenario still makes sense.
Paystack47

Search Customers

Search

In Make“Lists available customers.”

Search Customers pulls the customers stored in your Paystack account, so the scenario can find who already exists before creating anyone new.

When to use it
before Create a Customer, when a sign-up form may come from someone who already paid you once.
Watch out
several matches mean several bundles, and each module placed after the search runs once per bundle, so the operations add up faster than expected.
Paystack48

Search Dedicated Accounts

Search

In Make“Lists available dedicated accounts.”

Here the scenario sees the dedicated accounts already created in Paystack, which is the way to check whether a customer has one before assigning another.

When to use it
ahead of Create a Dedicated Account, when a returning customer may already have an account attached to their record.
Watch out
the search gives a list; when you need the details of a single account, Get a Dedicated Account is the module for that.
Paystack49

Search Disputes

Search

In Make“Lists disputes filed against you.”

A scattered backlog becomes a list: Search Disputes brings back the disputes filed against you, ready for the scenario to walk through and hand to the team.

When to use it
when finance reviews open cases, or when you catch up on disputes that arrived before Watch Disputes was switched on.
Watch out
if what you need is a file to share rather than bundles to process, look at Export Disputes instead.
Paystack50

Search Invoices

Search

In Make“Lists the invoices available on your integration.”

Search Invoices gives the scenario the invoices held on your Paystack integration, so it can pick the ones to follow up, archive or copy elsewhere.

When to use it
when invoices should live in a spreadsheet or a CRM too, and you want to start from what Paystack already holds.
Watch out
to remind a customer about one invoice, pass it to Send a Notification; to put an old one away, Archive an Invoice handles that.
Paystack51

Search Products

Search

In Make“Lists available products.”

Your Paystack catalog comes back as a list, so the scenario can compare it with your shop or price sheet before creating or changing anything.

When to use it
before Create a Product, to avoid adding an item that already sits in the catalog under the same name.
Watch out
each product found is its own bundle; if Update a Product follows, make sure only the product you mean reaches it, and test with Run once first.
Paystack52

Search Refunds

Search

In Make“Lists available refunds.”

Accounting sees in one pass what went back to customers: Search Refunds returns the refunds already issued in Paystack.

When to use it
when you reconcile payments and refunds in a sheet, or check that a refund promised by support was actually created.
Watch out
look a payment up here before calling Create a Refund on it; a second refund created by mistake could send money out twice.
Paystack53

Search Subscriptions

Search

In Make“Lists available subscriptions.”

The scenario receives the subscriptions on your account, the list it needs to spot customers to contact or plans to adjust.

When to use it
when expired cards pile up and you want to pass the affected subscriptions to Send an Update Subscription Link.
Watch out
anything placed after the search acts on every result; before Disable a Subscription, narrow the list so only the subscriptions you mean get through.
Paystack54

Search Transfers

Search

In Make“Lists the transfers made on your integration.”

Search Transfers lists the payouts made on your integration, a clean starting point for a payout report or a check that each supplier got paid.

When to use it
when the finance team closes its books and wants every transfer copied into its ledger or a shared sheet.
Watch out
the search shows transfers as they stand; to hear about new ones as they happen, Watch Transfers is instant and reports successful, reversed and failed transfers.
Need help

Need help automating Paystack with Make?

A person reads every message.

FAQ

Paystack and Make: common questions

01Is the Paystack Make integration free?
Yes, on the Make side. Paystack is a standard app, available on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and allow unlimited active scenarios. Make counts each module run as an operation against your monthly credits. You still need an active Paystack account, and its own pricing is set by Paystack.
02What do you need to connect Paystack to Make?
An active Paystack account and its Secret Key. In the Paystack Dashboard, go to Settings, open the Developers tab, choose API Keys and Webhooks and copy the Secret Key. In Make, add a Paystack module, click Create a connection, give it a name if you like and paste the key. For triggers, which are all instant, click Create a webhook before Create a connection. The same connection then serves every Paystack module in your scenarios.
03Do Paystack triggers in Make fire in real time?
Yes. All 7 Paystack triggers are instant: Paystack calls Make through a webhook as soon as the event happens, with no polling interval to wait for. That covers customer identifications, disputes, invoices, payment requests, subscriptions, successful transactions and transfers. Remember to create the webhook when you add the trigger, otherwise Paystack has nowhere to send the event. The scenario still has to be switched on to receive anything, and each event then runs it once.
04What if a Paystack module is missing in Make?
Use Make an API Call. With the same Paystack connection, it calls any endpoint of the Paystack API, so you can cover what the 61 listed modules leave out in your process. You write the request yourself, following Paystack's API documentation, and test it with Run once before you rely on it. If a module exists but behaves differently from what you expected, read the bundles it returned in that test run first. Keep in mind that the Make documentation for this app is AI-generated from Paystack's docs, so verify critical details with Paystack before a scenario moves real money.
05Should you use Make or n8n for Paystack?
It depends on the tool your team already runs. On Make, Paystack comes with 61 ready modules, 7 of them instant triggers, plus Make an API Call for the rest. Apps covered by Make often have an n8n node too, so check the n8n side for Paystack before choosing. Compare the modules each tool offers for the tasks you actually need, how you prefer to build, and the plan that fits your volume, rather than a general ranking.
Same platform

Other docs you might need on this stack.

Browse all integrations