--- title: "Tranzila Integration" description: "Tranzila is an Israeli payment processor for cards, Bit, and MASAV bank debits. Agents charge, verify, capture, and refund cards, complete 3DS flows, manage standing orders, create hosted-page handshakes and payment requests, and pull transaction reports and invoices." url: https://flowrunner.ai/integrations/tranzila date_modified: 2026-09-04T14:51:36-07:00 --- # Tranzila [Payments](https://flowrunner.ai/integrations/category/finance-accounting) Tranzila is an Israeli payment processor for cards, Bit, and MASAV bank debits. Agents charge, verify, capture, and refund cards, complete 3DS flows, manage standing orders, create hosted-page handshakes and payment requests, and pull transaction reports and invoices. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 22 actions · Custom auth · available [Tranzila website](https://www.tranzila.com/) · [Platform Documentation](https://docs.tranzila.com/) · Capability data verified 2026-08-25 1. The monthly collection cut-off arrives for customers who pay by bank debit 2. Agent assembles the shekel amount due per customer from the receivables ledger 3. Agent confirms each account is genuinely on the bank-debit arrangement and that no invoice on it is in dispute 4. The run is compared against last cycle so changed amounts and new accounts are separated from the routine ones 5. The controller receives the totals, the accounts that moved, and when the next clearing broadcast leaves 6. The controller approves the run, and only then does the agent submit the bank debits ## What This Integration Enables Tranzila is an Israeli processor, and the local instruments are the point rather than a regional footnote. Card payments carry tashlumim, where issuer-funded credit pays you the whole sum while the customer pays over time, and installments are a separate plan again. Standing orders can be index linked, so the price follows the Consumer Price Index with a base month and an optional floor. Bit, the country's dominant peer-to-peer app, is a first-class payment surface meant to be embedded rather than redirected to. And MASAV, the inter-bank clearing system, lets you charge a bank account directly with no card involved at all. Each of those instruments has a different story about taking money back, and the differences are not cosmetic. A card charge from today is canceled cleanly and leaves nothing on the statement, while the same charge tomorrow becomes a separate credit the customer sees twice. A Bit refund taken soon and in full cancels the payment outright, and any other shape appears as a credit. A MASAV charge, once the file has gone out, has no API route back at all. FlowRunner agents hold those rules per instrument and act on them at machine speed. The one that cannot be undone stops and asks, because [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) belongs where the reversal does not exist. ### Without FlowRunner **One undo story assumed for everything**: Cards, Bit payments, and bank debits are handled as if a refund means the same thing on each **Amounts trusted from the browser**: The payment page runs on the customer's device, so whatever it submits is what gets charged **Reports rebuilt from exports**: Finding every forced transaction above a threshold with a given order reference means pulling a file and filtering it by hand ### With FlowRunner **Each instrument handled by its own rules**: A same-day card void, a Bit refund, and a bank debit each follow the path that actually exists for them **Amounts locked before the page loads**: A handshake fixes the sum on Tranzila's side, and a tampered figure is rejected rather than charged **Reports queried where they live**: Core fields and your own terminal's custom fields are filtered with operators in a single call ## Use Case Scenarios ### A booking hold that is actually released A reservation needs a card held rather than charged. The agent calls Verify Card in hold-funds mode, which reserves the amount against the cardholder's limit and takes nothing. When the booking is honored, Capture Authorization collects it, using the id the verification returned. When the booking is canceled, Reverse Authorization releases it, and that call is the one that matters most: without it the hold sits against the customer's credit limit until the issuer expires it, which the customer experiences as their money being taken. The agent watches for holds that are neither captured nor released and escalates them, because an uncaptured hold is a sale you never collected and a customer quietly out of pocket. ### An invoice document that reaches the customer safely A payment settles. The agent calls Create Document to issue the tax invoice or receipt, tying it to the transaction so reconciliation is possible later, and takes the retrieval key from the response. Get Document URL turns that key into the public link, which is what goes into the email sent through [SendGrid](https://flowrunner.ai/integrations/sendgrid). The agent treats that link the way the platform does: the key is long and unguessable, and that is the only thing protecting the document, so it goes to the customer's address and nowhere else, and it is regenerated rather than stored indefinitely. Credit notes follow the same path with the related document number attached. ### A reconciliation report the finance team can actually run Month end asks a specific question: every forced transaction above a threshold carrying an order reference from one campaign. The agent reads the terminal's user-defined field slots first, because the filterable names are the terminal's own parameter names rather than the captions shown in the interface, which are often in Hebrew. It then runs the transaction report with operators on both core and user-defined fields, gets item lines included, and writes the result to [Google Sheets](https://flowrunner.ai/integrations/google-sheets) with the summary posted to [Slack](https://flowrunner.ai/integrations/slack). Nobody exports a file and filters it by hand. ## Human-in-Loop Highlight Create MASAV Charge is unlike every other operation on this connector, and the difference is not technical. A card charge can be canceled today or credited tomorrow. A Bit payment can be refunded. A MASAV charge is queued for the next inter-bank clearing broadcast, and the vendor states that once the file has gone out, a credit or a cancellation has to be arranged directly with the bank. There is no API to undo it. The route also differs in shape from everything around it, on its own host, form encoded, with the terminal called something else, which is a fair signal that it belongs to a different system with different rules. So the collection run does not submit itself. The agent builds it, prices it, compares it against the previous cycle, and posts the result to the controller: "142 accounts, 318,400.00 ILS, next broadcast 16:00 today. 4 accounts changed since last cycle: 3 increases totaling 2,180.00 and one new account at 890.00. 2 accounts have an invoice in dispute and are excluded. Submit?" The controller reads the four that moved rather than the hundred and thirty-eight that did not, approves, and the agent submits. A wrong amount here is not a support ticket. It is a phone call to a bank and a customer whose account was debited for something they did not owe. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 22 actions ### Transactions 7 - **Charge Card** Takes money from a credit card. There is no amount field: the charge is the sum of the item lines, so a transaction with no items charges nothing and still reports success. - **Refund Card** Puts money back on a card as a credit, which settles as a separate outgoing transaction the customer sees alongside the original charge. Tying it to the original is what keeps it from being a standalone credit. - **Verify Card** Three operations sharing one name: check the card exists, hold funds against it, or initialize a standing order. Which one you get is decided by the mode, and the hold is the one that reserves money. - **Capture Authorization** Collects money previously reserved by a hold. This is the step people forget, and an uncaptured hold eventually lapses with the sale never collected. - **Cancel Transaction** Voids a charge or a credit before it settles. Preferred to a refund while the transaction is still of today, because a cancellation leaves nothing on the customer's statement. - **Reverse Authorization** Releases held funds without collecting them, which is what a canceled booking needs. Without it the hold sits against the customer's credit limit until the issuer expires it. - **Complete 3DS Transaction** Finishes a card transaction that required an additional authentication challenge. Until it is called the payment is not complete, whatever the customer's browser showed them. ### Standing Orders 3 - **Create Standing Order** Sets up a recurring charge against a tokenized card. Index linking makes the price follow the Consumer Price Index from a base month, with an optional floor so it does not fall below the base. - **Update Standing Order** Changes a standing order's status, price, or index linkage. Sending items deletes and replaces all of them, so changing one line means sending every line. - **List Standing Orders** Searches standing orders by id, status, customer details, card token, last four digits, or bank account. It is the only read in this surface, so it is how an id is found before an update. ### Bit 2 - **Init Bit Payment** Starts a payment through Bit. The returned page is meant to be embedded rather than redirected to, showing a scannable code on desktop and a phone prompt on mobile, and the server-to-server confirmation is the one to trust. - **Refund Bit Payment** Returns money taken through Bit. A full refund close to the purchase cancels the payment outright, while a partial one or a later full one appears as a separate credit, and either way the customer is notified. ### Hosted Pages 1 - **Create Handshake Token** Locks a transaction amount on Tranzila's servers before the customer's browser loads the payment page, so a tampered amount is rejected rather than charged. Your own request parameters are stored with it and handed back on completion. ### Payment Requests 1 - **Create Payment Request** Sends a customer a request to pay by email, text, or both, with Tranzila building and delivering the page. Several fields the vendor marks required are easy to miss, and payment methods are numeric codes rather than names. ### MASAV 1 - **Create MASAV Charge** Charges a bank account through Israel's inter-bank clearing system. It does not take money immediately, it is shekels only, and once the file has gone out there is no API route to undo it. This is the operation this page's human gate exists for. ### Reports 3 - **Get Transactions** Returns past transactions for a terminal by date range or by a single index. A range is capped per page, so the total in the response matters more than the page in front of you. - **Get Transaction Report** Returns transactions with item lines and filtering on both core fields and your own user-defined fields, each with its own operator. This is what turns a specific question into a single call. - **List Terminal Fields** Returns the user-defined field slots and how your terminal has configured them. The parameter names it returns are what the report filters take, rather than the captions shown in the interface. ### Invoicing 4 - **Create Document** Issues a tax invoice, receipt, or credit note. It lives on a separate host and reports failure differently from the payment routes, and tying it to a transaction is what makes reconciliation possible. - **Get Document** Fetches one document by id, returning the file itself on success and structured data only when it fails. - **List Documents** Searches issued documents, and uniquely on this API it accepts several terminals at once, so a merchant with multiple terminals gets one combined view. - **Get Document URL** Turns a document's retrieval key into the public link that serves it. The key is the only protection on that link, so it is treated as a secret and expected to expire. ## Frequently Asked Questions ### What can FlowRunner do with Tranzila? FlowRunner agents can run Charge Card, Refund Card, and Verify Card in Tranzila, plus 19 more actions. ### Does connecting Tranzila to FlowRunner require OAuth? Tranzila uses a custom authentication method to connect to FlowRunner. ### Can Tranzila trigger a FlowRunner workflow automatically? Tranzila doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Tranzila?** This integration exposes Tranzila to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/tranzila. Site index: https://flowrunner.ai/llms.txt