Hi Fivetran Support Team,

I’m currently using the standard Stripe connector and I’m running into an issue related to out-of-band / manual payments recorded in Stripe.

We have invoices that are marked as paid in Stripe, but the payment was recorded manually (“Paid out of band”). In the Stripe dashboard, these payments have IDs starting with pr_ (Payment Records), instead of the usual pi_ (Payment Intents).

The problem is that:

• These pr_ payment IDs do not appear in the payment_intent table.

• There is no payment_record table available in the replicated schema.

• We also don’t see any events or webhook-style tables exposed by the connector that would allow us to trace these records.

• The invoice table does not include a paid_out_of_band field either.

Because of this, we are unable to fully reconcile invoices paid externally and trace the corresponding payment record (pr_) using the current Stripe connector output.

Could you please help us confirm:

1. Whether Payment Records (pr_...) are supported or exposed in any table by the Stripe connector.

2. If so, which table/column should contain this information.

3. If not, whether there is a recommended way (within the Stripe connector) to identify or extract out-of-band payments beyond inferring them indirectly from invoices.

4. Whether enabling any additional schema objects or settings in the existing connector could surface this data.

Our goal is to build an auditable reconciliation between invoices and payments, including external/manual payments.

Thanks in advance for your help — happy to share example invoice IDs or connector details if needed.

Best regards,
Natalia