Integration pair

Avalara + Stripe

Use Avalara and Stripe together with Plandalf as the layer that ties checkout, payments, invoices, integrations, and lifecycle automation together.

Common setup

Most teams use Avalara as their tax layer and Stripe as their payment layer, with Plandalf in the middle handling the checkout, Offers, invoices, integrations, and the events that fire after a purchase.

See Avalara and Stripe docs for connection details.

Product surfaces behind this integration

This legacy integration URL now points builders toward the same product reality as the canonical app-pair guide: Offers, payment options, invoices, integrations, Automations, API docs, and webhooks.

The Numi offer editor showing layout, product, theme, automation, invoice, and settings controls.

The offer record connects the stack

Use Offers to define the product, price, checkout mode, invoice, and automation context before Avalara and Stripe receive events.

The Numi Stripe payment methods settings page showing card, wallet, bank transfer, and buy now pay later options.

Payment options stay tied to checkout

Avalara and Stripe should not split payment state from invoices, tax settings, or post-purchase events.

The Numi integrations settings page showing Stripe, PayPal, TaxJar, and Avalara connection options.

Integration settings remain visible

Confirm Stripe, PayPal, TaxJar, Avalara, and test-mode routing before sending the Avalara and Stripe path live.

Feature detail