> For the complete documentation index, see [llms.txt](https://help.peoplevine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.peoplevine.com/products/control-panel-overview/reports-overview/reconcile-stripe.md). # How to Reconcile Transactions with Stripe ### Before you begin (Prerequisites) * **Permissions**: Administrator, Supervisor, or Support. See: [How to Manage Users and Permissions](/products/control-panel-overview/admin-overview/manage-roles-permissions.md). * **Stripe connected**: Stripe must be linked as a payment processor. See: [How to Link a Payment Processor](/products/control-panel-overview/admin-overview/link-payment-processor.md). * **Stripe Dashboard access**: You need access to your Stripe Dashboard to view payouts and payment details. ### Key reconciliation fields Peoplevine provides three fields that connect a transaction to Stripe: | Peoplevine field | Holds | What it is | | ---------------- | ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `transaction_id` | Stripe Payment Intent (`PI_*`) | Stripe creates a Payment Intent every time Peoplevine sends a charge request. Peoplevine stores the PI\_ in this field — use it to look up a specific charge in the Stripe Dashboard. | | `batch_id` | Stripe payout ID (`PO_*`) | Set when Stripe pays out to the merchant. Groups all transactions included in a single bank deposit. | | `matched_on` | Date | The date the transaction was reconciled to a Stripe payout (when Stripe synced the `batch_id` back to Peoplevine). | A **Matched** tag appears on a transaction once it has been reconciled with a Stripe bank payout. ### How reconciliation works Payments flow through three systems: **Peoplevine → Stripe → Bank**. * **Peoplevine → Stripe** — every time Peoplevine sends a charge request to Stripe, Stripe creates a **Payment Intent** (`PI_*`). Peoplevine stores the PI\_ in the `transaction_id` field. That's the link between a Peoplevine transaction and the Stripe charge. * **Stripe → Bank** — when Stripe pays out to the merchant, Peoplevine receives the **payout ID** (`PO_*`) and stores it in the `batch_id` field. That's the link between a group of Peoplevine transactions and the bank deposit they were paid out in. The Instructions below cover how to walk through each link in the Control Panel and Stripe Dashboard. ### Instructions There are two common reconciliation workflows. **Workflow A — "Have my sales from a given period been paid to my bank?"** (sales-anchored) 1. Navigate to [**SELL > View Transactions**](https://control.peoplevine.com/transactions). > **Note (Pro Dash):** Navigate to **SELL > Transactions > View Transactions**. 2. Set the **Date Filter** to **Charged On** and the date range to the sales period you want to check. 3. To filter for Stripe-only payments, set **Payment Type** = Credit Card. This includes all Stripe transactions but does not distinguish between multiple Stripe processors. To filter by a specific processor, use the **Processor** filter instead. 4. Click **APPLY**, then **SHOW DATA**. Transactions with a **Matched** tag and a **Batch ID** (`PO_*`) have already hit the bank. 5. To verify a specific deposit, take the Batch ID and locate the matching payout in your Stripe Dashboard under **Payouts**. **Workflow B — "What payments hit my bank in a given period?"** (deposits-anchored) 1. Navigate to [**SELL > View Transactions**](https://control.peoplevine.com/transactions). 2. Set the **Date Filter** to **Matched On** and the range to the period you want to check. 3. Click **APPLY**, then **SHOW DATA**. The result lists every transaction that was reconciled to a bank payout in that range. 4. To open the matching payout in Stripe, use the **Batch ID** (`PO_*`) from any row. **Finding an individual transaction in Stripe** 1. On the Peoplevine transaction detail, locate the `transaction_id` (`PI_*`) — shown in the **Payment ID** section. 2. In the Stripe Dashboard, go to **Payments** and search for the PI\_ ID. 3. The Stripe payment detail page shows the full charge history, refunds, and dispute status for that transaction. **Manually tracking a transaction (Track Transaction)** If you want to mark a transaction as matched without waiting for Stripe to sync the `batch_id`: 1. Open the transaction in Peoplevine. 2. Enable the **Track Transaction** toggle (labeled "This transaction was matched to my processor reports"). 3. Enter the **Batch ID**, **Amount Matched**, and **Date Matched**. 4. Click **CONTINUE**. ### Stripe resync If a transaction's status differs between Peoplevine and Stripe (for example, declined in Stripe but still showing as processed in Peoplevine), resync the record from the transaction detail page: 1. Open the transaction in Peoplevine. 2. Scroll to the **Payment ID** section. 3. Click the **(Sync Update)** link next to the Payment Intent ID and the listed processor. ### What Happens Next * **Matched transactions** display the Matched tag and Batch ID in the transaction list, confirming they are reconciled to a bank deposit. * **Unmatched transactions** (no Matched tag) may need manual review — check whether the charge was successful in Stripe using the `transaction_id`. * **Next step**: To investigate a specific transaction's payment method, see: [How to See the Payment Method Used on a Transaction](/products/control-panel-overview/transactions-overview/view-transaction-payment-method.md). *Last updated: 2026-05-24* --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.peoplevine.com/products/control-panel-overview/reports-overview/reconcile-stripe.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.