What actions can I run in onPay?

17 actions are available, including "Get an Acquirer", "Get a Subscription", and "Get a Transaction", and more. Run them from any trigger in your automation stack — map fields once and they execute automatically.

Do I need to write code to automate this?

No. Most automations are built visually on the canvas by picking triggers, actions, and mapping fields. You can add custom JavaScript with Functions when advanced logic is needed — but it is never required.

Is the integration secure?

Yes. Connections are authenticated per account, credentials are encrypted at rest, and you can enforce approvals and team-level access controls on any automation.

onPay Integrations

Payment gateway for transactions, subscriptions, captures, and refunds. Sync onPay invoices, payments, and ledgers with CRM, billing, and ops tools.

Explore Documentation

GDPR
Data Encryption
2FA
Local Data Region

Watch SubscriptionsTriggers when a subscription is created or updated.
Watch Transaction EventsTriggers when transaction events occur.
Watch TransactionsTriggers when a transaction is created or updated.
Get an AcquirerRetrieves a specific acquirer.
Get a SubscriptionRetrieves a specific subscription by its identifier.
Get a TransactionRetrieves transaction events.
List AcquirersRetrieves a list of acquirers.
List ProvidersRetrieves a list of providers.
List SubscriptionsRetrieves all subscriptions.
List Transaction EventsRetrieves transaction history events from onPay. This endpoint is optimized for keeping systems in sync with the latest transaction activity and supports cursor-based pagination to avoid refetching already processed events.
List TransactionsRetrieves a list of transactions.
List WalletsRetrieves a list of wallets.
Cancel a SubscriptionCancels a subscription for a specified user or service.
Cancel a TransactionCancels a transaction.
Capture a TransactionCaptures a transaction.
Create a PaymentCreates a new payment.
Create a Transaction From a SubscriptionCreates a new transaction from a subscription.
Make an API CallPerforms an arbitrary authorized API call.
Refund a TransactionRefunds a transaction.
Update an AcquirerUpdates settings of an acquirer.

When to use onPay

Common scenarios where onPay automation saves time and reduces manual work.

React to "Watch Subscriptions" in onPay in real time: route the event into CRM, chat, ticketing, or any connected service.
Use "Get a Subscription" as an automated action in onPay so records stay consistent whenever something changes elsewhere in your stack.
Layer "Watch Transactions" from onPay with filters, transforms, and AI steps to build automations that match your exact business logic.

How to connect

Sign in and approve access — your password is never shared with WEXTL®, and you can revoke access from the provider at any time.

Full API documentation

You’ll be redirected to sign in and approve access — your password is never shared with WEXTL.

Connecting onPay to WEXTL®

Field	Type	Help
OnPay - Client ID / Registration Owner Domain	text	Client ID must be set to the domain name of the integration owner. Example values: yourcompany.com.

Use in workflow automation

Start from onPay’s Watch Transaction Events trigger and the run begins the moment there’s something new — no cron job to babysit, no one remembering to check.

Add Create a Transaction From a Subscription as the next step, then branch, filter or hand off to the rest of your stack. The whole path stays on one canvas your team can read.

This integration brings 20 ready-made steps for finance work, and every run records what went in and what came back.

onPay workflow on the canvas: Watch Transaction Events then Create a Transaction From a Subscription

Frequently asked questions

Common questions about automating onPay in your workflows.

onPay has 3 triggers, including "Watch Subscriptions", "Watch Transaction Events", and "Watch Transactions". Use them to start workflows the moment onPay events fire — no polling required.

Field

Type

Help

OnPay - Client ID / Registration Owner Domain

text

Client ID must be set to the domain name of the integration owner. Example values: yourcompany.com.

Use in workflow automation

Start from onPay’s Watch Transaction Events trigger and the run begins the moment there’s something new — no cron job to babysit, no one remembering to check.

Add Create a Transaction From a Subscription as the next step, then branch, filter or hand off to the rest of your stack. The whole path stays on one canvas your team can read.

This integration brings 20 ready-made steps for finance work, and every run records what went in and what came back.

onPay Integrations

When to use onPay

How to connect

Use in workflow automation

Frequently asked questions

onPay Integrations

When to use onPay

How to connect

Connect onPay to any app in workflows

Use in workflow automation

Frequently asked questions

Connect onPay to any app in workflows

Connect onPay to any app in workflows

Connect onPay to any app in workflows

onPay Integrations

onPay triggers and actions

When to use onPay

How to connect

Use in workflow automation

Frequently asked questions

What triggers does onPay support?

What actions can I run in onPay?

Do I need to write code to automate this?

Is the integration secure?

onPay Integrations

onPay triggers and actions

When to use onPay

How to connect

Connect onPay to any app in workflows

Use in workflow automation

Frequently asked questions

What triggers does onPay support?

What actions can I run in onPay?

Do I need to write code to automate this?

Is the integration secure?

Connect onPay to any app in workflows

Connect onPay to any app in workflows

Connect onPay to any app in workflows