1C:Enterprise (OData) and Checkout Integration

Demonstration of how apps are integrated in WEXTL workflow builder[4]

Connect 1C:Enterprise (OData) and Checkout 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 trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about 1C:Enterprise (OData) and Checkout

Detailed info you need to know about 1C:Enterprise (OData) and Checkout integrations in WEXTL. Explore which modules apps support and how you connect them.

  • 1C:Enterprise (OData)

    • Finance
    • 2 triggers
    • 37 searches
    • 38 actions

    Business management platform for accounting, trade, and manufacturing.[5]

  • Checkout

    • Finance
    • 3 triggers
    • 17 searches
    • 25 actions

    Global payment platform for accepting cards, wallets, and alternative payment methods.[6]

How to connect 1C:Enterprise (OData) to Checkout

Set up your 1C:Enterprise (OData) and Checkout integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between 1C:Enterprise (OData) and Checkout work in WEXTL?

WEXTL exposes actions and triggers for 1C:Enterprise (OData) and Checkout that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.

1C:Enterprise (OData) triggersCheckout actions

1C:Enterprise (OData) modules

  • Call an HTTP Service Reaches an HTTP service defined in your 1C configuration. Use Body Type with Body to send data in the format your service expects. Output includes Headers and Body.
  • Cancel a Document Posting Reverses posting for a document in 1C. Use Operational Mode to cancel in operational mode, or leave it blank for your configuration default.
  • Complete a Task Marks a task as completed in 1C and returns Completed with its Record Key.
  • Confirm Exchange Plan Changes Tells 1C that an exchange plan message arrived at a node, using the Message Number you received from Get Exchange Plan Changes. Output includes Confirmed.
  • Count Records Counts the records in an object list in 1C and returns the Count. Use Filter with an OData expression to count only matching records.
  • Create a Business Process Creates a business process record in 1C. Output includes the Number and Date. Use Additional Fields for values that are not listed.
  • Create a Calculation Type Registers a calculation type in a chart of calculation types, returning its Code and Description. Use Exchange Load Mode to skip the write-time handlers in 1C.
  • Create a Catalog Item Saves an item into a catalog in 1C. Use Data Load Mode to save it the way a data exchange does, skipping the usual save checks, and Additional Fields for unlisted fields.
  • Create a Characteristic Type Defines a characteristic type in a chart of characteristic types. Output includes its Code, Description and Is Group value.
  • Create a Document Creates a document in unposted state. Output includes its Number and Date, plus the Posted flag. Use Post a Document afterwards to post it.
  • Create a Task Creates a task in 1C. Output includes its Number and Date, plus its Completed flag.
  • Create an Account Records an account in a chart of accounts in 1C. Turn on Exchange Load Mode to write the way an exchange does, skipping write-time handlers, and use Additional Fields for unlisted fields.
  • Create an Exchange Plan Node Inserts a node into an exchange plan, returning its Code, Description, This Node flag and Sent Message Number.
  • Create an Information Register Record Writes a record into an information register in 1C and returns its Period. Use Data Load Mode to write it the way an exchange load does, skipping write-time handlers.
  • Delete a Business Process Removes a business process record. Set Expected Data Version to stop the removal if the process was modified after you read it. No rollback exists.
  • Delete a Calculation Type Deletes a calculation type from its chart in 1C and returns Deleted along with the Record Key. There is no going back.
  • Delete a Catalog Item Deletes a catalog item in 1C. Use Expected Data Version to have 1C refuse the delete when the item changed after you read it. No going back.
  • Delete a Characteristic Type Removes a characteristic type from its chart in 1C and reports the Record Key of the removed entry. Nothing is recoverable afterwards.
  • Delete a Document Removes a document. Use Expected Data Version to have 1C refuse it if the document changed since you read it. Recovery is not possible.
  • Delete a Task Removes a task record and returns Deleted with the Record Key. Nothing can be recovered.
  • Delete an Account Deletes an account, with Expected Data Version available to make 1C refuse the delete when the account changed since you read it. No rollback is available.
  • Delete an Exchange Plan Node Deletes an exchange plan node in 1C and returns Deleted with its Record Key. No recovery is possible.
  • Delete an Information Register Record Removes an information register record in 1C. Nothing restores it afterwards.
  • Get a Business Process Looks up one business process and shows its Number and Date.
  • Get a Calculation Type Fetches one calculation type from its chart, with Code, Description and Predefined Name values.
  • Get a Catalog Item Retrieves one catalog item. Use Fields to list the fields to return, such as Ref_Key and Description.
  • Get a Characteristic Type Loads one characteristic type, with its Is Group flag, Code and Description.
  • Get a Constant Reads the Value of a constant in 1C, such as Company Name.
  • Get a Document Fetches one document with its Number, Date and Posted value. Add field names to Fields to limit the result.
  • Get a Register Record Set Reads every record a given document wrote to a register, with Recorder, Recorder Type and Records.
  • Get a Register Slice Takes the latest or earliest slice of an information register. Use Slice to choose between them, and Period for the date to take it at.
  • Get a Task Retrieves one task with its Number, Date and Name.
  • Get Account Turnovers Reads debit and credit turnovers of an accounting register between Start Period and End Period. Use Group By Dimensions to break them down, and Debit Account Condition to focus on one debit account.
  • Get an Account Reads one account from a chart of accounts, with its Code, Description and Account Type.
  • Get an Exchange Plan Node Pulls one node of an exchange plan, with its Code, Description and Sent Message Number.
  • Get an Information Register Record Reads a single record of an information register, addressed by every dimension plus the Period. Output includes Period.
  • Get Exchange Plan Changes Forms an exchange message for a node and sends the changes recorded since the last confirmed message. Output includes the Changes Feed. Use Confirm Exchange Plan Changes with the same Message Number afterwards.
  • Get Extra Dimension Types Shows the extra dimension types defined on an accounting register. Use Limit to restrict the rows.
  • Get Recalculations Reads recalculation records of a calculation register, filtered by Condition on the register fields and trimmed by Limit.
  • Get Records with Extra Dimensions Queries accounting register records together with their extra dimensions. Bound it with Start Period and End Period, and ask 1C for only the first N records with First Records.
  • Get Register Balance and Turnovers Queries balance and turnover figures for a register, bounded by Start Period and End Period. Use Group By Dimensions to split the rows.
  • Get Register Turnovers Queries turnovers over the span from Start Period to End Period for accumulation or accounting registers. Use Group By Dimensions to break the totals down.
  • Get Scheduled Data Pulls scheduled data for a calculation register. Use Condition to filter by the register fields and Limit to trim the rows.
  • Get the Actual Action Period Gets actual action period data for a calculation register. Use Condition to filter by the register fields and Limit to cap the rows.
  • Get the Calculation Base Reads base data behind calculation register entries, shaped by View Points and by the main and base register dimensions.
  • Get the Register Balance Takes register balances at one date. Use Period for that date, or leave it blank for the current date, and Group By Dimensions to split the balances.
  • List Accounts Lists accounts in a chart. Use Filter to keep only matching accounts, and Limit to cap the count, with at most 10,000 read in one run.
  • List Business Processes Finds business processes of one type. Use Order By to sort them by a field, and Expand to load reference fields in full instead of just their key.
  • List Calculation Types Shows the entries of a chart of calculation types. Turn on Only Records You May Read to skip the ones hidden by access rules, which otherwise make 1C refuse the whole request.
  • List Catalog Items Reads catalog items. Use Fields to name the ones to return, and Filter with DeletionMark eq false to hide items marked for deletion.

Checkout modules

  • Accept a Dispute Accepts liability for a dispute, conceding it instead of contesting it.
  • Activate a Card Activates a card that was issued earlier. It is meant for cards that Create a Card made without activating them.
  • Anonymize an Applicant Anonymizes the personal data held for an applicant. Output includes the ID, External applicant ID and Modified on date.
  • Capture a Payment Captures funds for a payment that was authorized earlier. Use Amount to set how much is captured and Capture Type to mark it Final. Output is the Action ID of the capture.
  • Create a Card Issues a card for a cardholder, picking a Card Product ID and a Type such as virtual. Turn on Activate Card to activate it at once or Is Single Use for a one-time card. Output includes the Last four and Status.
  • Create a Cardholder Registers an individual as an issuing cardholder, from an Entity ID, First Name, Last Name and Billing Address. Use Residency Address and Document to add identity details.
  • Create a Customer Adds a customer identified by Email. Use Default to set the instrument saved by default and Metadata to store extra information. Returns the new ID.
  • Create a Payment Requests a payment or payout, described through Amount and Payment Type. Turn on Capture to take the funds immediately, and add a Reference for your own tracking. Output includes the new ID plus the Status.
  • Create a Payment Link Generates a hosted payment link for an Amount and Currency, with Billing details. Use Expires In to give it a lifetime in seconds and Reference to tag it. Output includes ID and Expires on.
  • Create a Transfer Moves funds from a Source to a Destination. Use Transfer Type to pick the kind of transfer and a Reference to follow it. Output has the transfer ID and Status.
  • Create an Applicant Creates an onboarding applicant. Use External Applicant ID for your own reference, External Applicant Name for the full name and Email for the contact address. Output includes the new ID.
  • Delete a Customer Deletes a stored customer profile from your Checkout.com account.
  • Enroll a Card in 3DS Starts 3DS enrollment for a card, with a Security Pair and Phone Number. Use Locale with a value such as en-US.
  • Get a 3DS Enrollment Checks how a card is enrolled in 3DS: its Locale, Phone number, Security question and Created date.
  • Get a Card Loads one issued card, with its Last four, Expiry month, Expiry year and Status.
  • Get a Cardholder Shows a cardholder, including First name, Last name, Email, Date of birth and addresses.
  • Get a Customer Finds a customer from a Customer ID or email address and returns the Name, Phone, Default and Instruments.
  • Get a Dispute Reads a dispute, including its Category, Amount, Reason code and Status.
  • Get a Payment Reads a payment or payment session, with its Amount, Currency, Payment type and Reference.
  • Get a Payment Link Checks a payment link through its Paylink Link ID. Output includes its Status, Amount, Currency and Expires on.
  • Get a Transaction Retrieves an issuing transaction with its Status, Transaction type, Card and Cardholder.
  • Get a Transfer Returns a transfer showing its Status, Transfer type, Reason codes, Source and Destination.
  • Get an Applicant Fetches the stored profile of an applicant, including the External applicant name and Email.
  • Get Dispute Evidence Pulls the evidence already submitted for a dispute. Each kind has a file and a text output, such as Invoice or receipt file and Invoice or receipt text.
  • Get Entity Balances Checks the currency balances of an entity. Output includes the Descriptor, Holding currency and Balances. Use Query to filter the accounts and With Currency Account ID to add the sub-account ID.
  • Get File Information Reads the Filename, Purpose and Size of an uploaded file, together with when it was uploaded, from its File ID.
  • Increment an Authorization Raises the authorized amount of a payment by Amount, or extends how long the authorization lasts when Amount is blank or 0. Output includes the Action ID and Expires on.
  • List Disputes Lists disputes, narrowed by the From and To dates of their last update, Statuses, Entity IDs or Payment ARN. Turn on This Channel Only to see just the channel of your key.
  • List Payment Actions Lists the actions recorded against one payment, each with its Type, Amount, Approved flag and Response summary.
  • List Payments Searches payments with a Query, plus From and To dates that must be supplied together. Output includes the ID, Amount, Currency and Status of each payment.
  • List Transactions Retrieves issuing transactions. Filter by Cardholder ID, Card ID, Entity ID or Status, and bound the dates with From and To.
  • Make an API Call Calls the Checkout REST API directly with a free-form request under your saved credential.
  • Provide Dispute Evidence Stores evidence for a dispute as files or text, such as Proof of Delivery or Service File and Invoice or Receipt Text. Use Merchandise or Service Description to say what was sold.
  • Refund a Payment Refunds a payment for an Amount under a unique Reference. Use Capture Action ID to refund one capture and Destination to refund to a bank account.
  • Reverse a Payment Reverses a payment. Add a Reference to label the reversal in your own records.
  • Submit Dispute Evidence Sends the evidence already attached to a dispute for review. Returns a Request ID.
  • Update a Cardholder Modifies a cardholder. First Name, Last Name, Email, Phone Number, Date of Birth and the address fields can all be changed here.
  • Update a Customer Edits a stored customer by Email, Name, Phone or Default.
  • Update an Applicant Revises an applicant. You can change the Email and External Applicant Name.
  • Update Card Details Changes a card by Card ID: its Reference, Metadata, Expiry Month and Expiry Year. Output is the Last modified date.
  • Upload a File Uploads a local file for disputes or verification. Use Purpose to mark it as dispute or arbitration evidence.
  • Void a Payment Voids a payment. Add a Reference or Metadata to tag the void.
  • Watch Disputes Polls for disputes that are recorded or updated and runs once for each. Use Limit to cap the results handled per cycle.
  • Watch Payments Searches payments on your schedule and starts a run for every payment found. Use Limit to bound how many results one cycle handles.
  • Watch Transactions Checks issuing transactions on a schedule and runs for each newly recorded one. Use Limit to set how many results a cycle handles.

Explore alternative integrations

There are other apps[9] supported by WEXTL that can be paired with 1C:Enterprise (OData) and Checkout integrations. Pick any from the list below if the current combination isn't the one you need.

Automate 1C:Enterprise (OData) and Checkout on WEXTL®

Claim your 3-day trial to build 1C:Enterprise (OData) with Checkout integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting 1C:Enterprise (OData) and Checkout.

How do I connect 1C:Enterprise (OData) and Checkout?

Connect your 1C:Enterprise (OData) and Checkout 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]

What can I automate between 1C:Enterprise (OData) and Checkout?

Example: when the "Watch New Catalog Items" trigger in 1C:Enterprise (OData) fires, WEXTL can "Accept a Dispute" in Checkout. 1C:Enterprise (OData) has 2 triggers (including Watch New Catalog Items and Watch New Documents). Checkout has 42 actions (including Accept a Dispute, Activate a Card, and Anonymize an Applicant). Add filters and transforms between steps when you need them.[1]

Can 1C:Enterprise (OData) trigger actions in Checkout, and Checkout in 1C:Enterprise (OData)?

Yes. The integration works in both directions. Use the triggers of each app to start a workflow and the actions of the other app to update it.[2]

Do I need to write code to integrate 1C:Enterprise (OData) and Checkout?

No. 1C:Enterprise (OData)-to-Checkout automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does 1C:Enterprise (OData) integrate with Checkout in real time?

Yes. Trigger-based automations start the moment 1C:Enterprise (OData) (or Checkout) fires a new event. Webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control.[7]

How long does it take to set up a 1C:Enterprise (OData) + Checkout integration?

A first automation typically takes 5–10 minutes: connect the credential of each app once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect 1C:Enterprise (OData) with Checkout?

You can build your 1C:Enterprise (OData) + Checkout automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the 1C:Enterprise (OData) and Checkout integration.

  1. 1C:Enterprise (OData) and Checkout integration source code, module specs and credentials implementation.
  2. Our 1C:Enterprise (OData) and Checkout integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for 1C:Enterprise (OData) and Checkout, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® visual workflow builder, anonymized data from our technical support team.
  5. 1C:Enterprise (OData) integration information
  6. Checkout integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted 1C:Enterprise (OData) and Checkout integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore 1C:Enterprise (OData) and Checkout, or get started