A platform transfer does not equal the customer charge

Find where the customer charge lives

Stripe Connect supports platforms and other businesses managing payments and moving money among multiple parties. Confirm that the arrangement actually uses Connect before applying its charge vocabulary. Multiple websites, vendors or bank accounts alone do not establish that model.

For a direct charge, the charge appears on the connected account. For a destination charge or separate charges and transfers, the charge appears on the platform. This determines which account’s payment record starts the reconciliation. A merchant-facing report may show only part of the arrangement; an absent charge in that view is not proof that the buyer never paid.

Record the charge type for the actual payment rather than assuming every payment on the platform uses the same model. Stripe allows platforms to use multiple charge types. The first useful decision is therefore which account and charge reference this particular payment belongs to, not which total looks closest to the merchant receipt.

Follow the distribution without counting a second sale

In the direct-charge model, a connected-account charge can carry an application fee that transfers to the platform. Do not require a separate incoming platform transfer as proof of the sale: the customer charge is already located on the connected account. Record the fee only when the actual records show it.

With destination charges, the platform creates the charge and funds transfer to the connected account as part of that arrangement. Stripe documents approaches where the platform fee is retained from the transfer amount or paid after the full amount is transferred. A transfer equal to the customer charge therefore does not, on its own, establish that the merchant had no platform fee.

With separate charges and transfers, the charge and the transfers are distinct operations. Transfers can distribute funds across connected accounts, and their relationships need not be one charge to one transfer. Use the actual linkage provided by the platform’s records. Matching a transfer to a charge solely because the date or amount is similar can create a false reconciliation.

Keep the customer payment and the allocation of that payment on different lines. Adding a customer charge and its linked transfer as if both were customer collections counts the same money at different stages. Likewise, do not subtract an application fee twice if the merchant amount being compared already reflects it. Establish what each reported amount represents before doing arithmetic.

Attach fees and later adjustments to the right account

An application fee charged by a platform is distinct from Stripe’s processing fees. Stripe’s documentation says fee behavior can depend on configuration, especially for direct charges. A gap between the charge and the transfer is not sufficient evidence of a particular processing fee or contractual rate. Locate the actual fee entry and the account bearing it, then connect it to the payment where the records permit.

Charge type also changes the balance debited for refunds and chargebacks. Stripe documents refunds and disputed payment amounts against the connected account for direct charges, and against the platform for destination charges and separate charges and transfers. Do not infer fee responsibility from the disputed amount alone; configuration can matter for direct-charge dispute fees.

A customer refund and a transfer reversal describe different movements. For the platform-charge models, Stripe documents that the platform can reverse transfers to recover refund costs from connected accounts. Keep the refund reference, any actual reversal and any application-fee adjustment separately linked. A refund record is not sufficient proof that a corresponding transfer reversal or fee adjustment occurred.

Retain timestamps and currencies on every linked record. A later adjustment belongs in the history even if it falls outside the period of the original charge. Where a relationship or amount is missing, preserve an unmatched line rather than creating a fee or adjustment to force equality.

Close the allocation question before the payout question

The reconciliation is useful when it identifies the customer charge, the connected merchant’s recorded allocation, separately documented fees and any later adjustments. An incoming connected-account transfer establishes a balance movement, not a bank deposit. If the remaining question concerns money reaching the bank, continue with the payout record as a separate stage.

When the platform view is the only source available, ask for the missing link: the charge location and type, the transfer-to-payment relationship, the fee already included in a reported net amount, or the reversal tied to a refund. Keep the request specific to the unmatched references. A platform’s technical charge configuration does not settle legal merchant-of-record status, accounting revenue treatment or product eligibility.

For a scoped Prism processing consultation, describe the platform arrangement, website, research-only products and the unexplained relationship without sending customer exports or account credentials. Ask to confirm the requested reconciliation assistance and responsibilities; scope, fees and terms are discussed before work. The provider retains its eligibility and account decisions. The inquiry receives email follow-up and is not an appointment, service purchase or application.

Platform charge-to-transfer map

Start with one actual customer payment and extend the map only through documented relationships. Record non-secret references, account labels, amounts and currencies in the blank column. Mark a movement not applicable only when the arrangement supports that conclusion; missing evidence stays unknown. Do not add charge and transfer amounts as two customer receipts.

Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.

These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.