1C:Enterprise (OData) and BTCPay Server Integration

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

Connect 1C:Enterprise (OData) and BTCPay Server 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 BTCPay Server

Detailed info you need to know about 1C:Enterprise (OData) and BTCPay Server 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]

  • BTCPay Server

    • Finance
    • 1 trigger
    • 72 searches
    • 77 actions

    Self-hosted Bitcoin payments: invoices, payment requests, payouts, stores, webhooks and lightning.[6]

How to connect 1C:Enterprise (OData) to BTCPay Server

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

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

WEXTL exposes actions and triggers for 1C:Enterprise (OData) and BTCPay Server 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) triggersBTCPay Server 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.

BTCPay Server modules

  • Activate an Invoice Payment Method Turns on one payment method of an invoice, such as BTC-CHAIN or BTC-LN, for payment.
  • Add a Store User Gives a user access to a store through a Role. Name the user by id or email, and turn on Require Invitation to send an invitation first.
  • Approve a Payout Approves a pending payout. Use Revision to guard against edits made meanwhile and Rate Rule to convert with a custom rate. A failed approval is not retried automatically.
  • Approve a User Approves a user account on the server. Turn off Approved to withdraw an approval again.
  • Archive a Payment Request Archives a payment request of a store so it is taken out of the active ones.
  • Archive a Pull Payment Stops further claims on a pull payment by archiving it.
  • Archive an Invoice Hides an invoice from the default invoice lists.
  • Broadcast a Wallet Transaction Sends a signed Transaction in raw form to the network through the on-chain Payment Method of a store. Failures here are not retried automatically.
  • Cancel a Payout Cancels a payout that has not been sent yet.
  • Cancel a Store Invitation Withdraws a pending invitation to a store.
  • Connect to a Lightning Peer Joins a Lightning node, either the server node or a store node, to another peer. Write the peer address as nodeid@host:port.
  • Create a Lightning Invoice Creates a BOLT11 invoice on a Lightning node for an Amount (millisats). Use Expiry (seconds) to set its lifetime and Private Route Hints to include private channels.
  • Create a Payment Request Issues a request for payment in a store using a Title and an Amount. Add an Expiry Date, a Reference ID or Allow Custom Payment Amounts.
  • Create a Pull Payment Sets up a pull payment of a total Amount in a Currency. Use Payout Methods to limit how claims are paid and Auto Approve Claims to skip manual approval. A failed setup is not retried automatically.
  • Create a Pull Payment Payout Claims a payout against a pull payment, sent to a Destination through a Payout Method ID. Leave Amount empty to claim the rest. A failed claim is not retried automatically.
  • Create a Store Starts a store named Name. Set Website, Default Currency or Brand Color to shape how it looks and behaves.
  • Create a Store Payout Queues a payout out of store funds to a Destination for an Amount. Turn on Approved to approve it at once, or attach it to a Pull Payment ID. A failed attempt is not retried automatically.
  • Create a User Creates an account from an Email. Use Password to set one, Is Administrator for admin rights and Send Invitation Email to invite the user.
  • Create a Wallet Transaction Builds an on-chain transaction to Destinations. By default it signs and BROADCASTS it, which spends funds. Turn off Broadcast to avoid sending. A failed run is not retried automatically.
  • Create a Webhook Makes BTCPay Server call an Endpoint URL when store events occur. Use Events to restrict which, and Secret to sign every delivery.
  • Create an API Key Makes an API key for your own account. Use Label to name it and Permissions to restrict what it can do. You read the API Key value once.
  • Create an API Key for a User Makes an API key on behalf of another user. Use Label to name it and Permissions to limit the access it grants.
  • Create an App Attaches an app to a store under an App Name, of a chosen App Type. Use Notification URL to receive payment notices.
  • Create an Invoice Issues an invoice in a store for an Amount and Currency. Set Buyer Email to tie it to a customer and Order ID to match your own order. If the run fails, it is not retried automatically.
  • Create an Offering Adds a subscription offering to a store under a Name. Use Features for a JSON list and Success Redirect URL to send customers elsewhere after signing up.
  • Create an Offering Plan Adds a plan to a subscription Offering with a Name, Price and Currency. Use Recurring Type to set the renewal cycle and Trial Days for a free start.
  • Delete a File Deletes an uploaded file on BTCPay Server.
  • Delete a Notification Removes one notification from your inbox.
  • Delete a Store Removes a store from BTCPay Server.
  • Delete a Store Payment Method Disconnects a payment option from your store.
  • Delete a Subscriber Deletes one subscriber of an offering. Use Customer Selector to say which.
  • Delete a User Deletes a BTCPay Server user account.
  • Delete a Webhook Detaches a webhook from a store.
  • Delete an App Deletes an app from a store in BTCPay Server.
  • Delete the Current User Deletes the account of the user that owns the credential. Turn on Confirm Deletion to proceed.
  • Get a File Reads an uploaded file with its Original Name and URL.
  • Get a Lightning Address Reads a Lightning address of a store by Username. You see its Min, Max and Invoice Metadata.
  • Get a Lightning Deposit Address Generates an on-chain Address that tops up a Lightning node.
  • Get a Lightning Invoice Reads an invoice from a Lightning node by Lightning Invoice ID, including its BOLT11 string and a Status that tells whether it was paid.
  • Get a Lightning Node Balance Reads how much funds a Lightning node holds, split into two parts by Onchain and Offchain.
  • Get a Lightning Node Info Reads a Lightning node and its Alias, Version, Block Height and Peers Count.
  • Get a Lightning Payment Fetches one payment of a Lightning node by Payment Hash. It shows the Status and Preimage.
  • Get a Notification Opens one notification from your inbox with its Type, Body and Link.
  • Get a Payment Request Retrieves a payment request with its Title, Amount and Expiry Date.
  • Get a Payout Checks a payout and shows its Destination, Revision and Original Currency.
  • Get a Pull Payment Loads a pull payment with its Amount, Currency and BOLT11 Expiration.
  • Get a Pull Payment LNURL Gives the LNURL for a pull payment in two forms, LNURL Bech32 and LNURL URI.
  • Get a Pull Payment Payout Reads a single payout that was claimed against a pull payment, with its Destination and Date.
  • Get a Rate Configuration Shows how a store converts rates, with the Spread, the Preferred Source and the Effective Script.
  • Get a Store Reads a store with its Name, Website and Logo URL.

Explore alternative integrations

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

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

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

Cancel anytime.

Frequently asked questions

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

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

Connect your 1C:Enterprise (OData) and BTCPay Server 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 BTCPay Server?

Example: when the "Watch New Catalog Items" trigger in 1C:Enterprise (OData) fires, WEXTL can "Activate an Invoice Payment Method" in BTCPay Server. 1C:Enterprise (OData) has 2 triggers (including Watch New Catalog Items and Watch New Documents). BTCPay Server has 149 actions (including Activate an Invoice Payment Method, Add a Store User, and Approve a Payout). Add filters and transforms between steps when you need them.[1]

Can 1C:Enterprise (OData) trigger actions in BTCPay Server, and BTCPay Server 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 BTCPay Server?

No. 1C:Enterprise (OData)-to-BTCPay Server 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 BTCPay Server in real time?

Yes. Trigger-based automations start the moment 1C:Enterprise (OData) (or BTCPay Server) 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) + BTCPay Server 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 BTCPay Server?

You can build your 1C:Enterprise (OData) + BTCPay Server 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 BTCPay Server integration.

  1. 1C:Enterprise (OData) and BTCPay Server integration source code, module specs and credentials implementation.
  2. Our 1C:Enterprise (OData) and BTCPay Server integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for 1C:Enterprise (OData) and BTCPay Server, 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. BTCPay Server 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 BTCPay Server integration page documentation. Used sources, the role of AI, and how the team validates the result.

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