STEP 1
Connect Checkout and Swish
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 Swish Integration
Build finance workflows between Checkout and Swish on a visual canvas — set up data fields sync between apps once and let data flow when events come automatically. Integration will work without code and your team will see the workflow inside WEXTL® builder.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Checkout and Swish
Detailed info you need to know about Checkout and Swish integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect Checkout to Swish
Set up your Checkout and Swish integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Checkout and Swish 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 Swish. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Checkout and Swish work in WEXTL?
WEXTL exposes actions and triggers for Checkout and Swish 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 triggersSwish 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.
Swish modules
- Cancel Payment RequestCancel a Swish payment request that has not yet been completed.
- Check Recurring Availability (Alias)Check if a user is eligible for recurring payments using their phone number.
- Check Recurring Availability (TIN)Check if a user is eligible for recurring payments using their tax identification number.
- Create ConsentCreate a consent request to allow recurring payments from a customer.
- Create Consent TokenCreate a consent token for recurring payments that can be used to open the Swish app.
- Create Payment RequestCreate a Swish payment request for a customer. The customer will receive the request in the Swish app and can approve the payment there.
- Create PayoutCreate a payout to send money to a Swish user.
- Create RefundCreate a refund for a completed Swish payment.
- Delete Scheduled PaymentDelete a scheduled recurring payment before it is processed.
- Generate Prefilled QR CodeGenerate a QR code with pre-filled payment details that the customer can review and confirm.
- Generate QR CodeGenerate a QR code for a Swish payment request that customers can scan to pay.
- Make An API CallPerforms an arbitrarily authorized API request.
- Retrieve ConsentRetrieve the details and current status of a consent.
- Retrieve Payment RequestRetrieve the details and current status of a Swish payment request.
- Retrieve PayoutRetrieve the details and current status of a Swish payout.
- Retrieve RefundRetrieve the details and current status of a Swish refund.
- Update Consent Callback URLUpdate the callback URL for an existing consent.
Explore alternative integrations
There are other apps [9] supported by WEXTL that can be paired with Checkout and Swish 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 Swish.
Connect your Checkout and Swish 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 Payment Request" in Swish. Checkout has 3 triggers (including Watch Disputes, Watch Payments, and Watch Transactions); Swish has 17 actions (including Cancel Payment Request, Check Recurring Availability (Alias), and Check Recurring Availability (TIN)). 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-Swish 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 Swish) 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 + Swish 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 Swish integration.
- Checkout and Swish integration source code, module specs and credentials implementation.
- Our Checkout and Swish integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Checkout and Swish — 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
- Swish integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library