STEP 1
Connect Debitura and onPay
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow [3]. No coding or API skills required.
Debitura and onPay Integration
Connect Debitura and onPay to automate finance workflows. Trigger events from one app, run actions in the other and use AI to make smart decisions. Integrate apps in 3 simple steps - no code required.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Debitura and onPay
Detailed info you need to know about Debitura and onPay integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect Debitura to onPay
Set up your Debitura and onPay integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Debitura and onPay nodes onto the canvas [4], or describe what you want and WEXTL wires the flow together with AI Builder.
STEP 3
Map your data
Choose which fields need to sync between Debitura and onPay. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Debitura and onPay work in WEXTL?
WEXTL exposes actions and triggers for Debitura and onPay that help you connect apps and automate repetitive tasks [1]. A trigger is an event that happens, an action — a step that performs when the event has occurred.
Debitura triggersonPay actions
Debitura modules
- Create a CaseCreates a new case in the system.
- Get a CaseRetrieves case details by ID.
- Get a Case by ReferenceRetrieves a case's details by a case reference.
- Get a Case TimelineRetrieves a case timeline.
- Get a PaymentRetrieves a single payment from an account.
- List Case ChatsReturns all chat messages for a case.
- List Case FilesReturns all files for a case.
- List Case PaymentsReturns all payments for a case.
- List PaymentsRetrieves a list of payments from an account.
- Make an API CallPerforms an arbitrary authorized API call.
- Search CasesReturns a filtered list of cases.
- Upload a File to a CaseUploads a new file to a specified case.
- Watch CasesTriggers when new cases with a specified status are detected.
- Watch PaymentsTriggers when a new payment is received.
- Watch Updated CasesTriggers when a case has been updated.
onPay modules
- 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.
- 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.
- Make an API CallPerforms an arbitrary authorized API call.
- Refund a TransactionRefunds a transaction.
- Update an AcquirerUpdates settings of an acquirer.
- 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.
Explore alternative integrations
There are other apps [9] supported by WEXTL that can be paired with Debitura and onPay integrations. Pick any from the list below if the current combination isn't the one you need.
Frequently asked questions
Common questions about connecting Debitura and onPay.
Connect your Debitura and onPay accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them. [3]
Example: when Debitura's "Watch Cases" fires, WEXTL can "Cancel a Subscription" in onPay. Debitura has 3 triggers (including Watch Cases, Watch Payments, and Watch Updated Cases); onPay has 17 actions (including Cancel a Subscription, Cancel a Transaction, and Capture a Transaction). Add filters and transforms between steps when you need them. [1]
Yes — the integration works in both directions. Use each app's triggers to start a workflow and the other app's actions to update it. [2]
No. Debitura-to-onPay automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic. [4]
Yes. Trigger-based automations start the moment Debitura (or onPay) fires a new event — webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control. [7]
A first automation typically takes 5–10 minutes: connect each app's credential once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.
You can build your Debitura + onPay automation on a 3-day trial with every feature unlocked. Cancel anytime. For your protection, a small deposit is charged to your card when your trial starts. It counts toward your first payment and is non-refundable. [8]
References
List of sources used to gather information about the Debitura and onPay integration.
- Debitura and onPay integration source code, module specs and credentials implementation.
- Our Debitura and onPay integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Debitura and onPay — 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.
- Debitura integration information
- onPay integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library