STEP 1
Select onPay in workflow
Pick onPay app in the workflow builder [4] - just one click to select the app.
onPay Integration
Payment gateway for transactions, subscriptions, captures, and refunds. Sync onPay invoices, payments, and financial records with CRM, billing, and operations tools. When Watch Subscriptions arrives, automatically continue with Get a Subscription or Get a Transaction.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Supported triggers and actions for onPay integration
Triggers can detect changes in onPay and run actions that can create, search or modify data inside onPay automatically [3] — exactly how you set them.
- 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 a SubscriptionRetrieves a specific subscription by its identifier.
- Get a TransactionRetrieves transaction events.
- Get an AcquirerRetrieves a specific acquirer.
- 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.
How to integrate onPay in automation workflow?
3 simple steps to make your onPay connected with other apps in automation workflows on WEXTL. Up to 10 minutes integration set up.
STEP 2
Connect onPay
When prompted, authorize access to onPay in WEXTL once. onPay credentials are encrypted and never shared with WEXTL. Authorization will be reused in any future API calls [3].
WEXTL wants to integrate with your onPay account. Approve?
STEP 3
Build a workflow
Build your workflow with onPay yourself or with WEXTL® AI Builder. Connect onPay to any available integrations [5], or use HTTP node to go beyond them.
onPay
How onPay connects and integrates with WEXTL
Save and approve your credentials once — WEXTL® stores authorization information encrypted and reuses the authentication whenever onPay app is called in workflows. That allows your finance automations to run without your attention, per defined schedule [7]. Explore documentation [6] for a detailed list of fields that onPay supports.
The following table illustrates what fields onPay integration require during authorization flow inside our workflow builder [4].
Video slide demonstrates how onPay is connected in WEXTL builder [4].
| 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. |
Connect onPay to popular apps on WEXTL
Enter a name of the other app you want to sync with onPay below. Click on selected app to explore integration options with onPay. If the app you search for is not available in WEXTL yet, you can use HTTP node [10] instead to integrate it directly.
Example automation with onPay integration
Select Watch Transaction Events trigger from onPay - this will be a starting point in your automation. Whenever event happens in onPay, workflow will start [7] from Watch Transaction Events node.
Search for Create a Transaction From a Subscription, connect it as the next step of integration sequence. You can use filters between Watch Transaction Events and Create a Transaction From a Subscription, so only important data pass from Watch Transaction Events to the next step. WEXTL gives you full control over the process of onPay automation. All parts of workflow are visible on the canvas [4].
onPay on WEXTL has 20 modules for building finance automations. Explore onPay documentation for more.
Video slide demonstrates how Watch Transaction Events and Create a Transaction From a Subscription [6] nodes are used in onPay workflow.
Frequently asked questions
Common questions about automating onPay in your workflows.
onPay has 3 triggers, including "Watch Subscriptions", "Watch Transaction Events", and "Watch Transactions". Triggers are start points of the workflow, and automations may start from them.
Integration has 17 actions, including "Get a Subscription", "Get a Transaction", and "Get an Acquirer", and more. Refer to our onPay Documentation for detailed inputs and outputs.
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 our customers do that in rare cases [4].
Yes. Connections are authenticated per account, credentials are encrypted at rest, and you can enforce approvals and team-level access controls on any automation.
The onPay integration on WEXTL runs directly on its vendor public API — every field name, authentication method, and rate limit is controlled by onPay official API and covered in documentation [3]. WEXTL handles the request signing and pagination for you.
Absolutely. Where onPay provides native webhooks, you can use instant triggers to eliminate polling delay. For custom webhooks, WEXTL offers Custom Webhook node, so you can start automation whenever onPay or any other service sends event to webhook URL.
WEXTL is an AI-first visual canvas. The platform allows you to describe automation in plain text — and AI will wire nodes for onPay inside the workflow builder [4]. You can also use built-in workflow nodes (AI Agent, Human in the Loop, Condition, Aggregate Results) in pair with onPay modules to craft complex integration flows with branches, filtering, and conditional logic. There are absolutely no limits of what you can build.
References
List of sources used to gather information about the onPay integration.
- onPay integration source code, module specs and credentials implementation.
- Internal onPay integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official onPay vendor API documentation — used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® Visual Workflow Builder, anonymized data from our technical support team.
- WEXTL® Apps Library
- WEXTL® onPay App Documentation
- WEXTL® Workflow Scheduler
- WEXTL® HTTP node documentation