Reading Stripe Payment Logs
Review every Stripe charge, refund, dispute, and subscription event for your workspace, with direct links to Stripe records.
Stripe payment logs are the canonical record of every payment event that flowed between TrustPager and your connected Stripe account — charges, refunds, disputes, and subscription events. Each row links to the underlying Stripe object so you can drill into the source of truth when needed.
Where to find it
Go to https://app.trustpager.com/data/payments. Each row shows:
- Event type (charge succeeded, refund created, dispute opened, subscription updated, etc.)
- Customer name and email
- Amount and currency
- Status
- Linked TrustPager record (opportunity, order form submission, etc.)
- Stripe object ID
- Timestamp
Inspecting an event
Click any row to see:
- The full Stripe payload (with secrets redacted)
- Direct link to view the object in your Stripe dashboard
- Any TrustPager records that were updated as a result
- Automations that fired in response
- Receipt and dispute history if applicable
How TrustPager and Stripe stay in sync
Your Stripe account sends webhook events to TrustPager whenever something happens — a payment succeeds, a customer disputes a charge, a subscription renews. TrustPager processes these events and updates the relevant CRM records. The log records every event whether or not it produced a downstream change.
If your TrustPager records and Stripe data ever diverge, this log is the first place to check. The most common cause is a webhook event that arrived during an outage and didn't process — re-process it from the row detail and the records will reconcile.
Common event types
- charge.succeeded / payment_intent.succeeded — a payment was captured
- charge.refunded — a refund was issued
- charge.dispute.created — a customer disputed the charge with their bank. Treat this as urgent — check the contact and respond via Stripe.
- customer.subscription.updated — subscription plan, status, or quantity changed
- invoice.payment_failed — a recurring payment failed. Stripe will retry; your CRM is updated when it eventually succeeds or finally fails.
Filtering
Filter by event type, status, customer, amount range, or date range.
Related logs
For order-level detail (which products were bought, what automations fired), see https://app.trustpager.com/data/order-forms. To connect Stripe in the first place, see https://trustpager.com/help-center/how-to-connect-stripe.
Retention
Stripe event logs are retained for 90 days. Underlying Stripe objects are retained by Stripe according to their own retention policy.