Costs and account terms

A reserve entry belongs to a platform balance rather than the merchant balance

Start with the account to which the report belongs, then read the balance transaction's type, reporting category and originating source. A reserve label in a platform report does not establish that the same amount was held from the merchant's connected account. Stripe maps reserve_transaction to connect_reserved_funds and reserved_funds to risk_reserved_funds; those are different technical categories. Locate the actual entries and any documented counterpart before asking what the merchant's agreement says about the hold or release.

For: An owner or operations lead at a research-only merchant reconciling reserve-related records received through a platform or connected payment arrangement.

Updated 2026-10-01

Locate the account before interpreting the label

A report can show a familiar store name while still describing activity on an account operated by a platform. Identify the report's account context, the account role and the balance being reported. Use account references within the authorized records to distinguish the platform from the connected account; a public brand name or a filename is not enough.

Record the reporting period and currency with that identity. Keep platform and connected-account records separate while tracing the movement. If the report does not identify its account or balance context, the first unresolved question is which account the entry belongs to. Do not allocate it to the merchant simply because it arrived in the merchant's monthly statement bundle.

The title describes a possible finding, not a conclusion about your account. The evidence may show a platform entry, a connected-account entry or a report whose scope is still unclear. Each finding leads to a different follow-up.

Keep transaction type and reporting category as separate fields

Stripe's balance-transaction documentation uses type to describe the balance movement and source to identify the originating object. It recommends reporting_category for grouping transactions. Preserve all three where available; replacing them with the single word reserve discards the distinction this investigation needs.

Stripe's reporting-category table maps reserved_funds to risk_reserved_funds, while reserve_transaction maps to connect_reserved_funds. Copy the literal values from the real entry before assigning it to either group. The presence of Connect terminology supports classification of the movement; the report's account context is still needed to locate the balance.

The balance-transaction documentation also distinguishes risk reserve, network reserve and payout minimum balance types. Do not combine every unavailable amount into the same reserve total. This page does not decide accounting treatment or whether a technical category corresponds to the contractual reserve described in the merchant's agreement.

Trace related movements without inventing a second loss

Use the originating source and the report's available references to trace the actual movement. Record its amount, currency, direction and date in the authorized reconciliation records. Then look for a documented counterpart in the relevant balance records. Matching amounts alone are not sufficient to declare two entries paired, especially when reports cover different periods or accounts.

Stripe describes reserve_hold and reserve_release as counterparts in the reserve balance to reserved_funds. Where the records establish that relationship, do not count both sides as separate losses. That documented relationship does not mean every reserve_transaction entry is the counterpart of a merchant's reserved_funds entry. Keep an unproven connection marked as unpaired.

Charge type provides additional context, not a substitute for the reserve record. With Stripe Connect, direct charges appear on connected accounts; destination charges and separate charges and transfers place the charge on the platform, with different transfer arrangements. The charge model affects which balance pays refund or dispute debits. Identify the model actually used for the relevant activity before assuming the customer charge and the merchant's balance movement occurred on the same account.

Ask about release only after identifying the movement

When the report clearly locates a reserve entry on the platform, state that finding narrowly: this entry is reported on the platform's identified balance. Look separately for evidence of any corresponding effect on the merchant's balance. An absent merchant entry in an incomplete export does not prove there was no effect, and a platform entry alone does not establish a deduction from the merchant.

Connect the located movement to the actual notice or agreement by its references and dates. Ask the platform or provider to explain the relationship if the documents do not connect them. The resulting question should identify the account role, category and unpaired or unexplained movement, then ask which term and record govern it. Technical labels do not establish ownership of funds, contractual liability, release rights or a release date.

A Prism processing consultation can start with a non-sensitive summary of the arrangement and the unresolved provider question. The processing service page covers organizing the business facts for that conversation; scope, responsibilities, fees and terms are confirmed before work. Do not send raw account exports or bank details through the public inquiry. Contractual rights need the applicable agreement and qualified advice, not a conclusion drawn from this map.

Connected reserve location map

Complete the map for one real reserve-labelled movement. Use non-sensitive internal labels here and keep exact account and transaction references in authorized records. A confirmed platform location does not by itself establish a merchant hold. Leave counterpart and contract links unresolved unless the records actually connect them.

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.

Connected reserve location map. The last column is for temporary notes.
Location checkEvidence to compareInterpretation to preserveYour finding
Account identityThe report's account reference, platform or connected role, named balance, period and currency; summarize with an internal label.A platform report and a merchant report must not be merged merely because both mention the same store.
Reporting categoryThe entry's literal type and reporting_category values.reserved_funds maps to risk_reserved_funds; reserve_transaction maps to connect_reserved_funds. Category does not replace account identity.
Originating movementThe source object reference and the entry's direction, date and currency in the authorized report.Use the source to trace the origin; do not infer it from the word reserve alone.
Paired balance entryAny documented counterpart, the balance containing it and the record that establishes the connection.reserve_hold/release can be counterparts to reserved_funds; a similar amount does not prove pairing across accounts.
Charge-model contextThe actual direct, destination, or separate charge-and-transfer arrangement relevant to the records.Locates the charge and provides refund/dispute debit context; it does not determine reserve release rights.
Merchant balance effectThe merchant's own available record of the corresponding movement, or a precise missing-record description.Separate a verified merchant effect from an assumption based on the platform's entry.
Contract or provider questionThe notice or agreement reference and the specific link between account, movement and term that remains unexplained.Ask for that missing relationship; do not turn a category name into a release date or legal conclusion.

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.

Limits

  • These Stripe Connect and reporting labels apply to the documented Stripe arrangement; another platform or provider may use different meanings.
  • Movement location and category do not establish legal ownership, merchant-of-record status, tax treatment, contractual liability or release timing.
  • Stripe technical documentation does not establish that Stripe supports the merchant's products, country or processing arrangement.
  • Keep card data, credentials, full bank details, identity documents and raw account exports out of the worksheet and public consultation form.

Sources

  • Stripe balance transaction types — checked 2026-09-29. Stripe uses type for balance movements, source for the originating object and reporting_category for grouping. Reserve types differ; reserve_hold/release are reserve-balance counterparts to reserved_funds and should not be counted as separate losses. Labels do not establish release rights or timing.
  • Stripe reporting categories and types — checked 2026-09-29. Stripe maps reserved_funds to risk_reserved_funds and reserve_transaction to connect_reserved_funds. These reporting categories describe technical movements, not universal accounting conclusions.
  • Stripe Connect charge types — checked 2026-09-29. Direct charges appear on connected accounts; destination charges and separate charges/transfers place charges on the platform with different transfer arrangements. Charge type affects refund/dispute debit location, without deciding legal status or product eligibility.
  • Prism solutions — checked 2026-09-21. Published support is a storefront review, processing preparation, and help with a provider's website questions. Scope, fees, and terms are discussed before work. The provider decides eligibility and account terms.

Discuss my processing options

Want to talk through your own processing situation?