Skip to documentation content
Carden

Carden documentation

Choose an accounting or payment integration, then follow its ordered setup, API, and troubleshooting path.

On this page

Build from the provider you are implementing

Carden connects authoritative invoice data to merchant-owned payment workflows. QuickBooks supplies invoice facts. Stripe and Square are payment destinations whose payment credentials and execution stay in the merchant's backend. Merchants configure a Stripe webhook endpoint to deliver signed payment events directly to Carden; Square outcomes can be reported as optional observations.

From source facts to verified savings

Each handoff is independently observable and no earlier step substitutes for settlement evidence.

  1. Source

    Read invoice facts

    QuickBooks or another authoritative source supplies references, lines, tax, amounts, and balances.

  2. Prepare

    Create provider context

    Carden validates those facts and returns supported Stripe or Square request fields.

  3. Pay

    Run the merchant payment

    The merchant backend executes the provider operation with its own credentials and idempotency policy.

  4. Confirm

    Record the outcome

    Signed Stripe webhook events confirm payment activity; Square and other flows may use merchant observations.

  5. Reconcile

    Verify settlement economics

    Separate settlement evidence establishes qualification, actual cost, and reproducible savings.

Choose a provider

Accounting source

QuickBooks Online

Connect a company, sync authoritative invoices, inspect source evidence, and resolve factual exceptions.

Payment destination

Stripe

Prepare supported fields, attach them to the existing Stripe request, and confirm activity through signed Stripe webhook events.

Payment destination

Square

Prepare factual Order context, execute Orders and Payments in your backend, and report outcomes.

Payment destination

Braintree

Prepare Level 2/3 fields for your own Braintree transaction and record evidence from signed Braintree webhooks.

All integrations

Compare accounting-source and payment-destination responsibilities.

Shared platform and developer guidance

Platform and operations

Manage environments, permissions, logs, delivery, evidence, and security.

Developer tools

Configure authentication, shared HTTP conventions, errors, and webhooks.

Getting started

Connect providers one at a time and validate each boundary.

Rules for financial data

  • Use invoice facts from the source or an evidence-backed merchant mapping.
  • Store monetary amounts as integer minor units with a currency.
  • Keep source matching, transformation, processor acceptance, network qualification, and settlement measurement separate.
  • Persist payment attempts and report events before relying on network delivery.
  • Keep ambiguous provider outcomes unknown until reconciliation establishes the result.