What Stripe data does Well pull into Pennylane?

Stripe streams charges, refunds, payouts, customers, disputes, and subscription events to Well over its MCP server. After Well resolves the counterparty and assigns a confidence score, the matched record posts to Pennylane as supplier and customer invoices via email-in, with amount, VAT, and date pre-filled by Pennylane's OCR, with the Stripe event ID preserved on the entry for audit.

Will every Stripe record post to Pennylane automatically?

Not always. Within seconds of Stripe firing the event, Well scores the record on field completeness, counterparty strength, and policy fit. Above the 85% default auto-link threshold Well forwards the reconciled document to your Pennylane email-in address and Pennylane drafts the record from it for you to confirm. Between 55% and 85% the record waits in the review queue with the alternative matches ranked. Below the 55% default review threshold the record is refused and the candidate list kept so you can pin the right entry by hand.

How does Well prevent duplicates when posting Stripe records to Pennylane?

Stripe sends each event with a stable resource ID that Well tracks against the Pennylane ledger. Webhook replays (which Stripe can issue for delivery retries) are recognised by ID and either skipped or used to update the existing Pennylane entry. Distinct records that look similar are caught by Well before posting, with the candidates surfaced in the review queue when confidence is ambiguous.

What happens if a Stripe record fails to post to Pennylane?

When a record fails to post to Pennylane (validation rule, missing field, transient 5xx), Well retries automatically with backoff. Auth failures short-circuit the retry loop and notify the workspace owner; schema rejections are kept on the integration status page with a one-click retry-after-fix action pointing back at the original Stripe record. Nothing silently drops.

What happens if I disconnect Stripe or Pennylane?

Disconnecting Stripe stops the flow at the source. Well asks the Stripe MCP server to revoke the access token; Stripe returns confirmation and stops streaming events the moment it is acknowledged. Anything you already reviewed and posted in Pennylane is Pennylane's own record and is untouched; Well never held a write credential to it. Records held for review in Well remain in the queue so you can finish them by hand. Reconnecting later resumes from the last successful sync, not from scratch.

How does Well authenticate with Stripe and Pennylane?

Stripe's MCP server handles authorisation directly; Well receives an access token through Dynamic Client Registration and never sees raw user credentials. For the delivery side, Well forwards the reconciled document to your Pennylane email-in address once it clears the matching threshold; Pennylane creates the draft record from it and you confirm and post it. Well holds no write credential to Pennylane. Tokens are encrypted at rest and in transit under TLS 1.3. Pennylane hosts in the EU and Stripe hosts outside the EU; Well processes records per the storage region configured for your workspace.

Stripe to Pennylane

AvailableNative · StripeNative · Pennylane

Connect Stripe to Pennylane with Well

Every Stripe charge collapses onto the right customer match inside Well; the resulting documents arrive at Pennylane as drafts with vendor, amount, and date pre-filled by Pennylane's own OCR.

Connect both toolsView all integrations

Stripe

Source

The Stripe integration connects your payment infrastructure to Well via MCP, pulling charges, invoices, subscriptions, refunds, and payout data into your workspace automatically.

Pennylane

Target

The Pennylane integration creates a bidirectional bridge between Well and your accounting workspace.

Why this pair

Stripe and Pennylane disagree about almost everything.

Stripe thinks in charges and payouts; Pennylane thinks in customer and supplier invoices with VAT lines. Connecting them through Well bridges that vocabulary gap. Every Stripe charge is matched inside Well to a customer record, every payout is decomposed into its component charges with fees and tax split onto the right context, and each matched document is forwarded to Pennylane's email-in address so Pennylane creates the invoice with amount, VAT, and date pre-filled by its OCR.

What Well does between Stripe and Pennylane

One-way: Stripe into Well into Pennylane
Sync mode: Real-time MCP push
Events arrive in seconds

Trigger from Stripe

14 events · pick one

Well engine·recipe·When a Stripe charge succeeds

Source

from payment · live webhook

Pixel Foundry

via Stripe

Charge

When a Stripe charge succeeds

ch_1q5nk · 22 Apr 2026€1,284.00

Extract

6 fields read from Stripe

6 fields read

CustomerPixel Foundry
Charge date22 Apr 2026
Charge amount€1,284.00
CurrencyEUR
Processing fee€37.24

Enrich

against your historical record graph

4 fields added

Customer recordPixel Foundry
Domainpixelfoundry.studio
Tax idFR98765432101
Sales journalVE · 2026

Confidence97%

<55% refused55–85% review≥85% auto-posts

Post

post as supplier and customer invoices

Create a supplier invoice in Pennylane

auto-posted

posted

TypeSupplier invoice
VendorPixel Foundry
Amount€1,284.00
LedgerVE · 2026
Source docattached
Confidence97%

audit linkto Pennylane

Action in Pennylane

2 compatible with this trigger

Create a supplier invoice in PennylaneResolve a Pennylane supplier from the document

Reconcile Stripe multi-currency charges to Pennylane entries.

01Featured

Resolve refund and dispute writebacks

Refunds and chargebacks from Stripe land as reversing entries in Pennylane the moment the dispute is opened, with the original charge auto-linked so the audit trail keeps both sides of the trade. The reversal carries the dispute reason so the accounting team does not have to dig through Stripe to write the note.

Bring multi-currency charges into one ledger

Each Stripe charge keeps its original transaction currency on the matched document. Well stamps the FX rate at the timestamp of the event and attaches both the source and converted amounts to the document forwarded to Pennylane, so the draft your team confirms stands up to audit.

Surface jurisdiction for tax-code routing

Stripe charges carry the customer billing country in their metadata; Well stamps the jurisdiction (EU / US / AU / etc.) on the document forwarded to Pennylane, with reverse-charge context on cross-border charges so your team can apply the right tax code in Pennylane in one click.

Decompose fees from a card payment

Every Stripe card charge is split inside Well into the gross amount, the processor fee, and the net deposit. The fee context is broken out on the document forwarded to Pennylane, ready for your team to route it onto the processor-fee account on confirmation.

19 signals and actions across Stripe and Pennylane

When a Stripe customer is created
Pulls from the Stripe events feed. Pulls new customer records with name, email, and tax id where set. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Company
When the processing fee on a Stripe charge is recorded
Pulls from the Stripe events feed. Pulls the fee from the charge's balance transaction so net revenue is correct. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Transaction
When a Stripe charge fails
Pulls from the Stripe events feed. Captures failed charges so you can chase the customer or retry. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Transaction
When a Stripe dispute is opened
Pulls from the Stripe events feed. Captures the dispute with the contested charge and dispute reason. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Transaction
When a payment intent settles
Pulls from the Stripe events feed. Detects successful payment intents and links the captured charge to the intent. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Transaction
When a Stripe payout is created
Pulls from the Stripe events feed. Triggers on every payout batch with the underlying charges and fees. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Transaction
When a Stripe subscription starts
Pulls from the Stripe events feed. Tracks new subscription records with cadence, amount, and customer. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Invoice
When a Stripe subscription cycle renews
Pulls from the Stripe events feed. Detects renewal cycles and links the new invoice to the recurring contract. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Invoice
When a Stripe customer is updated
Pulls from the Stripe events feed. Detects changes to customer name, billing address, or tax id. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Company

Reference

Field mapping for Stripe → Pennylane

15 fields across 3 record types, open to see the full table.

Transaction fields

5 fields flow from Stripe into Pennylane.

Stripe field	Label		Pennylane field	Label
charge.amount	Charge amount	→	amount	Amount
charge.currency	Currency	→	currency	Currency
charge.created	Charge date	→	date	Execution date
charge.description	Description	→	label	Label
charge.id	Charge id	→	external_reference	Source id

Invoice fields

7 fields flow from Stripe into Pennylane.

Stripe field	Label		Pennylane field	Label
invoice.currency	Currency	→	currency	Currency
invoice.number	Invoice number	→	label	Reference
invoice.issue_date	Issue date	→	date	Invoice date
invoice.due_date	Due date	→	deadline	Due date
invoice.tax	Tax total	→	vat_amount	VAT
invoice.subtotal	Subtotal	→	pre_tax_amount	Subtotal
invoice.customer	Customer reference	→	external_reference	Source id

Company fields

3 fields flow from Stripe into Pennylane.

Stripe field	Label		Pennylane field	Label
customer.name	Customer name	→	name	Customer name
customer.tax_id	Tax id	→	vat_number	VAT number
customer.metadata.domain	Domain	→	website	Website

Connect Stripe and Pennylane in three steps.

1
Connect Stripe
Click Connect with Stripe; Stripe's MCP server handles authorisation. Stripe's MCP server registers a read-scoped Well client through DCR; no credential paste, no shared secret.
- AuthOAuth 2.0
2
Map your accounts
Well discovers Stripe's charges, refunds, payouts, customers, disputes, and subscription events and the the Pennylane Purchases tab and the customer-invoice collections list. Match candidates are scored on counterparty name, amount, currency, and reference; you approve any that need a human eye and Well saves the rule for the next batch.
- Auto-post above85% confidence
- Overridemanual anytime
3
Connect Pennylane
Click Connect with Pennylane; Well's OAuth proxy handles Pennylane authorisation through Dynamic Client Registration. Pennylane's MCP server registers a write-scoped Well client through DCR; no credential paste, no shared secret.
- AuthOAuth 2.0
- First syncup to an hour

How Stripe and Pennylane stay secure with Well

Well connects to Stripe through its MCP server, which issues short-lived access tokens via Dynamic Client Registration. Well never holds a long-lived Stripe secret; the server refreshes its own tokens on each session. Well processes records per the storage region configured for your workspace; only fields strictly required by the write surface are ferried across regions.

MCP server authEU residency optionGDPR-aligned

Scopes Well requestsmcp.stripe.com

Read Stripe records
Scoped to charges, refunds, payouts, customers, and related records. No access to anything else in your Stripe account.
granted
Deliver documents to your Pennylane inbox
Well forwards the extracted document to your Pennylane email-in address; Pennylane reads supplier and customer invoices via email-in, with amount, VAT, and date pre-filled by Pennylane's OCR from it and you review and post. No write credential to Pennylane is requested.
granted
Modify or delete Stripe records
Not granted. Stripe is read-only on Well's side; the source of truth never moves.
refused
Read other workspaces' data
Encryption keys are per-workspace; another tenant's records are inaccessible by design.
refused

Disconnect any time from Well settings or Stripe’s admin panel.

Frequently asked questions about Stripe and Pennylane on Well

01What Stripe data does Well pull into Pennylane?: Stripe streams charges, refunds, payouts, customers, disputes, and subscription events to Well over its MCP server. After Well resolves the counterparty and assigns a confidence score, the matched record posts to Pennylane as supplier and customer invoices via email-in, with amount, VAT, and date pre-filled by Pennylane's OCR, with the Stripe event ID preserved on the entry for audit.
02Will every Stripe record post to Pennylane automatically?: Not always. Within seconds of Stripe firing the event, Well scores the record on field completeness, counterparty strength, and policy fit. Above the 85% default auto-link threshold Well forwards the reconciled document to your Pennylane email-in address and Pennylane drafts the record from it for you to confirm. Between 55% and 85% the record waits in the review queue with the alternative matches ranked. Below the 55% default review threshold the record is refused and the candidate list kept so you can pin the right entry by hand.
03How does Well prevent duplicates when posting Stripe records to Pennylane?: Stripe sends each event with a stable resource ID that Well tracks against the Pennylane ledger. Webhook replays (which Stripe can issue for delivery retries) are recognised by ID and either skipped or used to update the existing Pennylane entry. Distinct records that look similar are caught by Well before posting, with the candidates surfaced in the review queue when confidence is ambiguous.
04What happens if a Stripe record fails to post to Pennylane?: When a record fails to post to Pennylane (validation rule, missing field, transient 5xx), Well retries automatically with backoff. Auth failures short-circuit the retry loop and notify the workspace owner; schema rejections are kept on the integration status page with a one-click retry-after-fix action pointing back at the original Stripe record. Nothing silently drops.
05What happens if I disconnect Stripe or Pennylane?: Disconnecting Stripe stops the flow at the source. Well asks the Stripe MCP server to revoke the access token; Stripe returns confirmation and stops streaming events the moment it is acknowledged. Anything you already reviewed and posted in Pennylane is Pennylane's own record and is untouched; Well never held a write credential to it. Records held for review in Well remain in the queue so you can finish them by hand. Reconnecting later resumes from the last successful sync, not from scratch.
06How does Well authenticate with Stripe and Pennylane?: Stripe's MCP server handles authorisation directly; Well receives an access token through Dynamic Client Registration and never sees raw user credentials. For the delivery side, Well forwards the reconciled document to your Pennylane email-in address once it clears the matching threshold; Pennylane creates the draft record from it and you confirm and post it. Well holds no write credential to Pennylane. Tokens are encrypted at rest and in transit under TLS 1.3. Pennylane hosts in the EU and Stripe hosts outside the EU; Well processes records per the storage region configured for your workspace.