STEP 1
Connect Checkout 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.
Checkout and onPay Integration
Keep Checkout and onPay in sync by integrating their events and actions. When finance events happen in Checkout, update the onPay automatically - without any line of code in visual workflow builder.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Checkout and onPay
Detailed info you need to know about Checkout and onPay integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect Checkout to onPay
Set up your Checkout and onPay integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Checkout 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 Checkout and onPay. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Checkout and onPay work in WEXTL?
WEXTL exposes actions and triggers for Checkout 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.
Checkout triggersonPay actions
Checkout modules
- Accept a DisputeAccepts liability for a dispute.
- Activate a CardActivates an issued card.
- Anonymize an ApplicantAnonymizes applicant personal data.
- Capture a PaymentCaptures an authorized payment.
- Create a CardIssues a new card.
- Create a CardholderCreates an issuing cardholder.
- Create a CustomerAdds a new customer.
- Create a PaymentRequests a payment or payout.
- Create a Payment LinkGenerates a hosted payment link.
- Create a TransferMoves funds between accounts.
- Create an ApplicantCreates an onboarding applicant in the system.
- Delete a CustomerRemoves a customer from the system.
- Enroll a Card in 3DSBegins the 3DS enrollment process for a card.
- Get 3DS EnrollmentRetrieves the 3DS enrollment status of a card.
- Get a CardRetrieves the details of a card.
- Get a CardholderRetrieves cardholder details from the service.
- Get a CustomerRetrieves customer details.
- Get a DisputeRetrieves a dispute.
- Get a File's InfoRetrieves uploaded file information.
- Get a PaymentFetches a specific payment.
- Get a Payment LinkRetrieves a payment link from the service.
- Get a TransactionRetrieves a transaction based on the specified criteria.
- Get a TransferRetrieves details of a transfer.
- Get an ApplicantRetrieves applicant details.
- Get Dispute EvidenceRetrieves evidence that has been submitted for a dispute.
- Get DisputesRetrieves all disputes.
- Get Entity BalancesChecks currency balances for a specific entity.
- Get Payment ActionsRetrieves actions performed on a payment.
- Get PaymentsRetrieves all payments.
- Get TransactionsRetrieves all issuing transactions.
- Increment AuthorizationIncreases the authorization amount for a transaction.
- Make an API CallPerforms an arbitrary authorized API call.
- Provide Dispute EvidenceUploads evidence for a dispute.
- Refund a PaymentIssues a refund for a specific payment.
- Reverse a PaymentReverses a payment transaction.
- Submit EvidenceSubmits dispute evidence for review.
- Update a CardholderUpdates cardholder information.
- Update a CustomerModifies customer information.
- Update an ApplicantModifies applicant information in the system.
- Update Card DetailsModifies card details for a specific card.
- Upload a FileUploads a file for disputes or verification.
- Void a PaymentVoids an existing payment in the system.
- Watch DisputesTriggers when a new dispute is recorded or an existing dispute is updated.
- Watch PaymentsTriggers when a new payment is registered.
- Watch TransactionsTriggers when new transactions are recorded.
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 Checkout 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 Checkout and onPay.
Connect your Checkout 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 Checkout's "Watch Disputes" fires, WEXTL can "Cancel a Subscription" in onPay. Checkout has 3 triggers (including Watch Disputes, Watch Payments, and Watch Transactions); 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. Checkout-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 Checkout (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 Checkout + 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 Checkout and onPay integration.
- Checkout and onPay integration source code, module specs and credentials implementation.
- Our Checkout and onPay integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Checkout 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.
- Checkout integration information
- onPay integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library