STEP 1
Connect Checkout and Frontstream
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 Frontstream Integration
Keep Checkout and Frontstream in sync by integrating their events and actions. When finance events happen in Checkout, update the Frontstream 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 Frontstream
Detailed info you need to know about Checkout and Frontstream integrations in WEXTL. Explore which modules apps support and how you connect them.
Frontstream
Payment processing platform for nonprofits managing donations, contracts, and card transactions. [6]
How to connect Checkout to Frontstream
Set up your Checkout and Frontstream integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Checkout and Frontstream 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 Frontstream. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Checkout and Frontstream work in WEXTL?
WEXTL exposes actions and triggers for Checkout and Frontstream 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 triggersFrontstream 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.
Frontstream modules
- Check Is Card Commercial TypeChecks whether the card number belongs to a commercial card.
- Create a ContractCreates a new contract.
- Create a CustomerCreates a new customer.
- Delete a ContractDeletes an existing contract.
- Delete a CustomerDeletes an existing customer.
- Get Card Transaction SummaryRetrieves a card transaction summary for a merchant.
- Get Returned Check ReportRetrieves a returned or rejected check transactions for a merchant.
- List Check Transaction DetailsRetrieves checks transaction details for a merchant.
- List Transaction DetailsRetrieves card transaction details for a merchant.
- List Transaction Type InfoRetrieves information peraining to the transaction type specified.
- Update a ContractUpdates an existing contract.
- Update a CustomerUpdates an existing customer.
- Validate a CardChecks whether a card is valid by number and expiry date.
- Validate a Card LengthChecks whether the card number length is valid.
- Validate a MOD10Checks whether the card MOD10 checksum is valid.
- Validate an Expiration DateChecks whether the card expiration date is valid.
Explore alternative integrations
There are other apps [9] supported by WEXTL that can be paired with Checkout and Frontstream 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 Frontstream.
Connect your Checkout and Frontstream 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 "Check Is Card Commercial Type" in Frontstream. Checkout has 3 triggers (including Watch Disputes, Watch Payments, and Watch Transactions); Frontstream has 16 actions (including Check Is Card Commercial Type, Create a Contract, and Create a Customer). 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-Frontstream 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 Frontstream) 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 + Frontstream 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 Frontstream integration.
- Checkout and Frontstream integration source code, module specs and credentials implementation.
- Our Checkout and Frontstream integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Checkout and Frontstream — 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
- Frontstream integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library