{"templateId":"openapi_docs","versions":[{"version":"v1","label":"v1","link":"/api-reference/v1/transactions","default":false,"active":true,"folderId":"1b9c9f54"},{"version":"v2","label":"v2","link":"/api-reference/transactions","default":true,"active":false,"folderId":"1b9c9f54"}],"sharedDataIds":{"openAPIDocsStore":"oas-api-reference/@v1/index.yaml","sidebar":"sidebar-sidebar.yaml__api-reference_v1"},"props":{"definitionId":"api-reference/@v1/index.yaml","dynamicMarkdocComponents":[],"baseSlug":"/api-reference/v1","seo":{"title":"Transactions","siteUrl":"https://developer.flute.com","description":"The Transactions endpoint group is the fundamental means of managing purchases and refunds.\nTransactions in general are separated into two divisions: **ACH transactions** and **cards transactions**.\n\n**ACH transactions** are payments processed through the ACH (automated clearing house) network.\nThese are direct bank-to-bank transfers such as debits and credits.\nThese transactions are typically processed in batches and settle or close within one to two business days.\n\nTo complete an ACH (automated clearing house) transaction, see <a href=\"#ach-transactions\">ACH Transactions</a>.\n\n**Card transactions** are payments processed using a credit or debit card.\nThese are processed through a card network such as Visa or Mastercard, among others.\nCard transaction operations support initiating the transaction, retrieving transaction details,\nand monitoring transaction status throughout processing.\nThis processing has additional steps, such as verifying available funds,\npossibly declining the transaction request, holding the funds, and finally settling the request.\n\nCard transactions are separated into two operations: **One-step operations** and **two-step operations**.\n\n**One-step operations** are transactions that authorizes and captures the transaction in a single request.\nThis allows processing a payment in one step or action by both approving the card and immediately completing the transaction.\nThis is a common retail situation when the purchase price is finalized and known at the moment of the sale.\n\n**Two-step operations** are transactions that authorize and capture the transaction in separate requests.\nCommon situations for this are:\n* A restaurant or hospitality situation.\nThe initial bill is known and a tip is added later.\nThe initial bill authorized and the funds held for a short while.\nAfter the tip is added, the transaction is completed.\n* An e-commerce or delayed fulfillment situation.\nThe purchase price is known but the customer order has a delay for fulfilment\nThe purchase price is authorized but the funds are put on hold.\nThe transaction is completed when the item is shipped.\n\n","lang":"en-US","llmstxt":{"hide":true,"excludeFiles":[]}},"itemId":"transactions","disableAutoScroll":true,"metadata":{"subType":"openapi-operation"},"compilationErrors":[],"markdown":{"partials":{},"variables":{"rbac":{"teams":["anonymous"]},"user":{},"remoteAddr":{"hostname":"developer.flute.com","port":4000,"ipAddress":"216.73.216.41"},"lang":"default_locale","env":{"PUBLIC_REDOCLY_BRANCH_NAME":"main"}}},"pagePropGetterError":{"message":"","name":""}},"slug":"/api-reference/v1/transactions","userData":{"isAuthenticated":false,"teams":["anonymous"]},"isPublic":true}