Resources · Zapier integration

PayJunction Zapier integrationAutomate PayJunction with Zapier.

The PayJunction Zapier integration gives you 6 triggers, 8 actions and 4 searches. Five of the triggers are instant, PayJunction is not a premium app, and this page covers what each operation does, what it costs and where it breaks.

See the 18 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the PayJunction Zapier integration does for a payments team

The PayJunction Zapier integration links your PayJunction account to Zapier, a tool that runs automations between apps. An event in PayJunction, such as a declined card or a new deposit, starts a sequence of steps, and those steps can also write back into PayJunction: a customer, an invoice, a recurring payment.

A follow-up on every declined card. New Failed Payment fires the moment a payment is declined, so the person who chases unpaid balances gets the case while the customer still remembers the purchase.

Receipts that leave on their own. New Transaction paired with Send Transaction Receipt Email mails the receipt to the address you choose, with a reply-to address of your own, so answers land in the right inbox.

Invoices and schedules created from other tools. Create Invoice, Create Customer and Create Recurring Payment let a form, a CRM or a spreadsheet produce the billing record in PayJunction instead of someone retyping it.

What Zapier does not do here: none of the 8 actions refunds, voids or deletes anything, so cancelling a payment stays a job for the PayJunction dashboard. Nothing that happened before the Zap went live is picked up either.

If you are still weighing up the tool itself, our Zapier review covers the platform as a whole, and the Make vs Zapier comparison sits next to it.

Vocabulary

The Zapier words this page uses

Eight terms, each in plain words. They come back all through the page without being explained twice.

Zap
The automation you build: one trigger, then one or more actions that run every time that event happens.
Trigger
The event in PayJunction that starts the Zap. Once the Zap is switched on, Zapier waits for it.
Action
The step that does the work once the Zap has started: it creates, sends or updates something for you.
Task
What Zapier bills: one action your Zap completes successfully. The allowance on your plan counts those.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself, so nothing waits for a check.
Filter
A step that lets the Zap carry on only when what arrived meets your condition, and stops it otherwise.
Search step
A step that looks up something already in PayJunction, such as a customer, so later steps can reuse what it found.
Connection
Your PayJunction account linked to Zapier once, then reused by every step that talks to PayJunction.
Cost

What a PayJunction Zap really costs

Zapier bills tasks, not Zaps. The trigger never costs anything, and neither does Zapier checking for new data, however often it looks.

  • Free plan100 tasks a month, two-step Zaps only
  • TriggerNever costs a task
  • Premium appNo, works on the free plan
  • Instant triggers5 of 6, unaffected by the grid below

Each action that succeeds counts as one task, so a Zap with three actions uses three times what a one-action Zap uses. A failed action is not counted. The free plan gives 100 tasks a month and unlimited Zaps, but only two steps per Zap: one trigger, one action. Add a filter, a search or a second action and the Zap becomes a multi-step Zap, which needs a paid plan. PayJunction itself is open on the free plan.

Connect

Connect your PayJunction account in three steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. You need a PayJunction account, plus access to anything you do not own yourself but want the Zap to read or change.

  2. 02

    Find PayJunction

    Type PayJunction in the search box of the dialog, pick it from the list, then click Add connection. A new tab opens on the PayJunction side, ready for you to sign in.

  3. 03

    Sign in and grant access

    Sign in to PayJunction in that tab and allow Zapier into the account. The connection is then saved, and every PayJunction step of every Zap reuses it.

First Zap

Your first PayJunction Zap, step by step

GoalEvery new transaction gets its Level 3 detail added, then the receipt is emailed to the customer.

  1. 01

    Pick the trigger

    Create a Zap, choose PayJunction as the app and New Transaction as the event, then select the connection you saved earlier.

  2. 02

    Test it on a real payment

    Run the trigger test. Zapier brings back the three most recent transactions of the account, so you map the next steps on a real one instead of a guess.

  3. 03

    Add the Level 3 detail

    Add Add Level 3 Data to Transaction. Map the transaction from the trigger into Transaction ID, then fill the item fields: description, product code, quantity, unit of measure, amounts.

  4. 04

    Send the receipt

    Add Send Transaction Receipt Email, map the same Transaction ID, and set Recipient Email and Reply-To Email. Both addresses are required.

  5. 05

    Test, then publish

    Test each step and read what came back. Then publish to switch the Zap on. With two actions this is a multi-step Zap, so it needs a paid plan.

Triggers

PayJunction triggers in Zapier

6 events start a Zap when something happens in PayJunction, and 5 of them are instant: the app calls Zapier straight away, whatever your plan.

1

New Deposit

Instant trigger

In Zapier“Triggers when a new deposit is created.”

Starts a Zap each time PayJunction records a new deposit, so finance hears about it from Zapier instead of spotting it later in the dashboard.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a bookkeeper who wants every deposit logged in the accounting sheet without opening PayJunction.
Watch out
deposits created before the Zap was published never come through, so your history needs a separate export.
2

New Failed Payment

Instant trigger

In Zapier“Triggers when payment transaction is declined.”

Reacts when a payment transaction is declined. This is the trigger that turns a silent failure into a to-do for someone on the team.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
alert the account manager or open a collections task when a card bounces, while the client is still reachable.
Watch out
the Zap only reacts to refusals that happen after it is switched on, so earlier failed payments stay out of the follow-up list.
3

New Invoice

Polling trigger

In Zapier“Triggers when a new invoice is created.”

Picks up each invoice newly created in PayJunction and hands it to the next steps of your Zap.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
copy every invoice into a shared tracker so sales can see what has been billed without a PayJunction login.
Watch out
this is the only trigger of the app that polls, so it is the one that lags behind the others on the free plan.
4

New Settlement

Instant trigger

In Zapier“Triggers when a new settlement is created.”

Fires when PayJunction creates a new settlement. It suits whoever reconciles the takings and wants to know a new one exists without checking.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
post each settlement to the finance channel so the person reconciling knows a batch is ready to match.
Watch out
if a Zap writes into the same place its trigger watches, it sets itself off again and burns tasks fast.
5

New Smart Terminal Status Update

Instant trigger

In Zapier“Triggers when a new smart terminal status update is received.”

Runs whenever a Smart Terminal reports a new status update. For a shop or a front desk, it is how a counter device gets a voice outside PayJunction.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
pair it with Create Smart Terminal Payment Request to follow what happens on the device after a payment is pushed to it.
Watch out
a busy terminal can report many updates, and every action they start counts against your tasks.
6

New Transaction

Instant trigger

In Zapier“Triggers when a new transaction is created.”

The broadest trigger of the app: any new transaction in the account starts the Zap. Most PayJunction automations begin here.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
send the receipt, add Level 3 detail or log the sale in a sheet, with the transaction already in hand.
Watch out
it catches every transaction, so add a filter if you only want some of them, which makes the Zap multi-step.
Actions

PayJunction actions in Zapier

PayJunction gives you 8 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Add Level 3 Data to Transaction

Action

In Zapier“Adds Level 3 data to a transaction.”

Attaches Level 3 line-item detail to a transaction: description, product code, quantity, unit of measure, discount and tax indicators, amounts.

When to use it
B2B sellers whose buyers pay by corporate card and expect itemised data on every charge.
Watch out
setting Override Existing Level 3 Data to true deletes the detail already there before adding the new one.
2

Create Customer

Action

In Zapier“Creates a new customer.”

Adds a new customer record to PayJunction from whatever started the Zap.

When to use it
a signup form or a new deal in your CRM creates the matching customer, so billing is ready before the first charge.
Watch out
if the same person may already be in PayJunction, put Find Customer first and decide what the Zap does when it finds a match.
3

Create Invoice

Action

In Zapier“Creates a new invoice, probably with input from previous steps.”

Builds a PayJunction invoice, usually from data an earlier step carried. Amount, Terminal ID and Customer Email are all required.

When to use it
a signed quote in another tool becomes an invoice the client can pay, without anyone retyping the amount.
Watch out
the terminal you set is the one that processes the payment once the invoice is paid.
4

Get Transaction Receipt

Action

In Zapier“Get a transaction receipt by ID.”

Retrieves the receipt of a transaction by its ID, and the Include setting decides which receipt types come back.

When to use it
fetch the receipt so a later step can file it in a shared folder or attach it elsewhere.
Watch out
without a trigger that carries the ID, add a Find Transaction step to get it first.
5

Create Recurring Payment

Action

In Zapier“Creates a new recurring payment.”

Sets up a recurring payment on an existing customer. It asks for a Schedule Type, a Customer ID and a Base Amount.

When to use it
a membership or retainer sold elsewhere turns into a PayJunction schedule on the spot.
Watch out
put a Find Customer step before it to get the Customer ID, and leave Bypass Duplicate off unless you mean it.
6

Send Transaction Receipt Email

Action

In Zapier“Sends a transaction receipt via email.”

Emails the receipt of a given transaction. It needs the Transaction ID, a Recipient Email and a Reply-To Email.

When to use it
after New Transaction, so every buyer gets a receipt and their replies reach your support address.
Watch out
Request Signature only works when the receipt is not signed yet.
7

Create Smart Terminal Payment Request

Action

In Zapier“Initiates a payment request on a Smart Terminal.”

Pushes a payment request to a Smart Terminal, with the base amount in dollars. Options cover a tip, a receipt prompt and a signature screen.

When to use it
a booking tool sends the amount due straight to the counter device when the client checks out.
Watch out
the debit or credit prompt only shows if the account supports PIN Debit.
8

Update Customer

Action

In Zapier“Updates an existing customer.”

Changes a customer that already exists in PayJunction. The only required field is the Customer ID.

When to use it
keep billing details in step when a client edits their profile in your CRM.
Watch out
the Zap must know which customer to touch, so Find Customer usually comes right before.
Searches

PayJunction searches in Zapier

4 search steps look for data that already exists in PayJunction, so a later step can use it.

A search step finds a record that already exists in PayJunction and passes it to the steps after it. In the editor, searches sit at the bottom of the Action event list, under SEARCH. PayJunction offers no find-or-create variant. Three settings decide what happens when the result is not a clean single match.

1

Find Customer

Search

In Zapier“Finds a customer based on name.”

Looks a customer up by name and returns the matching record to the next steps.

When to use it
just before Create Recurring Payment or Update Customer, both of which require that ID.
Watch out
two customers with the same name fall under the multiple-results setting, so pick its behaviour on purpose.
2

Find Invoice

Search

In Zapier“Finds an invoice.”

Retrieves an invoice that already exists in the account, so a later step can work on it.

When to use it
a payment reminder flow that needs the invoice before sending anything.
Watch out
if nothing matches and the default is kept, the rest of the Zap is skipped for that run.
3

Find Scheduled Payment

Search

In Zapier“Finds a scheduled payment based on status.”

Finds a scheduled payment from its status, which is handy for checking on recurring billing.

When to use it
before an account review, to see where a customer's schedule stands.
Watch out
a status can match many schedules at once, so set the multiple-results option deliberately.
4

Find Transaction

Search

In Zapier“Finds a transaction.”

Locates a transaction and hands over its Transaction ID to the next step.

When to use it
feed Get Transaction Receipt or Send Transaction Receipt Email when the trigger does not carry the transaction.
Watch out
it adds a step, so the Zap becomes multi-step and needs a paid plan.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, an empty search stops the Zap and skips the steps that relied on it. Switched on, the Zap carries on with nothing in hand.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create on apps that support it. PayJunction does not, so you will not see it here.
  3. If multiple search results are found?
    Keep the first match, which is the default, stop the Zap, or pass every match on at once.
When it breaks

When a PayJunction Zap breaks

Zapier links no help article to PayJunction, and no app-specific limit is documented. What breaks is what breaks on any Zap.

Four cases come back again and again. When a Zap misbehaves, our Zapier troubleshooting page is the next stop.

  • The past is never picked up

    A Zap only reacts to transactions, deposits or invoices that appear after it is switched on. Older records stay where they are, and moving them is a separate job.

  • A Zap that triggers itself

    If a Zap creates invoices and also starts on New Invoice, it sets itself off again and again, and the task count drains quickly.

  • A sudden flood is held back

    After a bulk import, a trigger that returns a huge batch at once can be held by Zapier's flood protection instead of running every item.

  • No double runs on New Invoice

    Zapier remembers what it has already seen on a polling trigger, so the same invoice does not start the Zap twice.
Need help

Need help automating PayJunction with Zapier?

A person reads every message.

FAQ

PayJunction Zapier integration: frequent questions

01Is the PayJunction Zapier integration free?
Yes, it works on the free plan, because PayJunction is not one of the premium apps that Zapier keeps for paid plans. The free plan gives 100 tasks a month and unlimited Zaps. The catch is the shape of each Zap: on the free plan a Zap is one trigger and one action, nothing more. If you want a filter, a search step or a second action, for example finding a customer before creating a recurring payment, the Zap becomes multi-step and you need a paid plan. Tasks themselves are counted the same way whatever the plan.
02How many tasks does a PayJunction Zap use?
One task per action that succeeds, and nothing for the trigger. A Zap that sends a receipt for every new transaction uses one task per transaction. If the same Zap also adds Level 3 data first, it uses two per transaction. Zapier checking for new invoices costs nothing, however often it looks, and an action that fails is not counted. A few apps and actions take more than one task when they complete, so a small margin on your monthly allowance is wise.
03Is PayJunction on Zapier real time?
For five of the six triggers, yes. New Deposit, New Failed Payment, New Settlement, New Smart Terminal Status Update and New Transaction are instant: PayJunction tells Zapier the moment the event happens, whatever your plan. New Invoice is the exception. It is a polling trigger, so Zapier checks on a timer: every 15 minutes on the free plan, every 2 minutes on Professional, every minute on Team and Enterprise. On a paid plan a check can also be run by hand from the editor.
04What does it take to connect PayJunction to Zapier?
A PayJunction account, and access to whatever records you want the Zap to read or change if you do not own them yourself. The connection is made once from the Apps page of Zapier with + Add connection, then you sign in to PayJunction in the tab that opens and grant access. After that, every PayJunction step in every Zap reuses it. Also check which terminals the account can use, because Create Invoice and Create Smart Terminal Payment Request both require a Terminal ID.
05Why does Add Level 3 Data to Transaction erase existing data?
Because of one setting. Override Existing Level 3 Data is a required field, and when it is set to true the action deletes the Level 3 data already on the transaction before writing the new detail. Left on false, it does not replace what is there. The trap is a Zap that runs twice on the same transaction, or a second Zap touching the same sales: with the override on, the last run wins. Decide which Zap owns the Level 3 detail before switching the override on.
06What if the PayJunction operation you need is missing?
Then Zapier cannot do it for PayJunction, and no setting will reveal it. The integration has 6 triggers, 8 actions and 4 searches, and none of them refunds, voids or deletes a payment. Those jobs stay in the PayJunction dashboard. What you can often do is combine existing steps: Find Customer then Update Customer, or Find Transaction then Get Transaction Receipt. If the gap is central to your process, it is worth checking what other automation tools offer for PayJunction before building around it.
07Zapier, Make or n8n for PayJunction?
It depends on what the PayJunction side has to do, so judge on criteria rather than a ranking. On Zapier you get 18 visible operations, five instant triggers and an app that works on the free plan, with Zaps limited to two steps there. Check whether the other tools cover the same events, especially declined payments and settlements, whether they report them instantly or by polling, and how each one bills a run that has several steps. The operation list is what usually settles it.
Same platform

Other docs you might need on this stack.

Browse all integrations