Transactions

A tax transaction is a committed sale: the calculation you quoted at checkout, locked in after the buyer paid. Invoice and NFS-e documents are under Invoicing, and the checkout sequence is under Integration.

Commit after payment

• Call commit only after payment authorization/capture succeeds - never before
• Pass the same taxCalculationId that was shown at checkout (from the PSP round-trip)
• Include merchantTransactionReference and payment details (paymentReference, processor)
• Sync validation checks structure only - authority clearance / e-invoice is asynchronous

Explicit pending / cleared / rejected status and clearance webhooks are on the roadmap - today, retrieve issued documents from Invoicing after commit.

Lookups & refunds

Fetch an existing transaction by ID when you need its committed amounts or identifiers. Create a refund transaction for line items you reverse, and list refunds on a transaction when reconciling. Card-rail payment refunds and chargebacks are a Payments concern - see Refunds & disputes.

API map

Schemas and examples live in the API reference.

• POST/api/tax/transactions
• GET/api/tax/transactions/{transaction_id}
• GET/api/tax/transactions/{transaction_id}/refunds
• POST/api/tax/transactions/{transaction_id}/refunds