PostChargesChargeDispute

Gross amount of this transaction (in cents (or local equivalent)). A positive value represents funds charged to another party, and a negative value represents funds sent to another party.

The date that the transaction's net funds become available in the Stripe balance.

The balance that this transaction impacts.

Time at which the object was created. Measured in seconds since the Unix epoch.

Three-letter ISO currency code, in lowercase. Must be a supported currency.

An arbitrary string attached to the object. Often useful for displaying to users.

If applicable, this transaction uses an exchange rate. If money converts from currency A to currency B, then the amount in currency A, multipled by the exchange_rate, equals the amount in currency B. For example, if you charge a customer 10.00 EUR, the PaymentIntent's amount is 1000 and currency is eur. If this converts to 12.34 USD in your Stripe account, the BalanceTransaction's amount is 1234, its currency is usd, and the exchange_rate is 1.234.

Fees (in cents (or local equivalent)) paid for this transaction. Represented as a positive integer when assessed.

Detailed breakdown of fees (in cents (or local equivalent)) paid for this transaction.

Unique identifier for the object.

Net impact to a Stripe balance (in cents (or local equivalent)). A positive value represents incrementing a Stripe balance, and a negative value decrementing a Stripe balance. You can calculate the net impact of a transaction on a balance by amount - fee

String representing the object's type. Objects of the same type share the same value.

Learn more about how reporting categories can help you understand balance transactions from an accounting perspective.

This transaction relates to the Stripe object.

The transaction's net funds status in the Stripe balance, which are either available or pending.

Transaction type: tax_fund, adjustment, advance, advance_funding, anticipation_repayment, application_fee, application_fee_refund, charge, climate_order_purchase, climate_order_refund, connect_collection_transfer, contribution, inbound_transfer, inbound_transfer_reversal, issuing_authorization_hold, issuing_authorization_release, issuing_dispute, issuing_transaction, obligation_outbound, obligation_reversal_inbound, payment, payment_failure_refund, payment_network_reserve_hold, payment_network_reserve_release, payment_refund, payment_reversal, payment_unreconciled, payout, payout_cancel, payout_failure, payout_minimum_balance_hold, payout_minimum_balance_release, refund, refund_failure, reserve_transaction, reserved_funds, reserve_hold, reserve_release, stripe_fee, stripe_fx_fee, stripe_balance_payment_debit, stripe_balance_payment_debit_reversal, tax_fee, topup, topup_reversal, transfer, transfer_cancel, transfer_failure, transfer_refund, or fee_credit_funding. Learn more about balance transaction types and what they represent. To classify transactions for accounting purposes, consider reporting_category instead.

Any server or activity logs showing proof that the customer accessed or downloaded the purchased digital product. This information should include IP addresses, corresponding timestamps, and any detailed recorded activity.

The billing address provided by the customer.

(ID of a file upload) Your subscription cancellation policy, as shown to the customer.

An explanation of how and when the customer was shown your refund policy prior to purchase.

A justification for why the customer's subscription was not canceled.

(ID of a file upload) Any communication with the customer that you feel is relevant to your case. Examples include emails proving that the customer received the product or service, or demonstrating their use of or satisfaction with the product or service.

The email address of the customer.

The name of the customer.

The IP address that the customer used when making the purchase.

(ID of a file upload) A relevant document or contract showing the customer's signature.

(ID of a file upload) Documentation for the prior charge that can uniquely identify the charge, such as a receipt, shipping label, work order, etc. This document should be paired with a similar document from the disputed payment that proves the two payments are separate.

An explanation of the difference between the disputed charge versus the prior charge that appears to be a duplicate.

The Stripe ID for the prior charge which appears to be a duplicate of the disputed charge.

A description of the product or service that was sold.

(ID of a file upload) Any receipt or message sent to the customer notifying them of the charge.

(ID of a file upload) Your refund policy, as shown to the customer.

Documentation demonstrating that the customer was shown your refund policy prior to purchase.

A justification for why the customer is not entitled to a refund.

The date on which the customer received or began receiving the purchased service, in a clear human-readable format.

(ID of a file upload) Documentation showing proof that a service was provided to the customer. This could include a copy of a signed contract, work order, or other form of written agreement.

The address to which a physical product was shipped. You should try to include as complete address information as possible.

The delivery service that shipped a physical product, such as Fedex, UPS, USPS, etc. If multiple carriers were used for this purchase, please separate them with commas.

The date on which a physical product began its route to the shipping address, in a clear human-readable format.

(ID of a file upload) Documentation showing proof that a product was shipped to the customer at the same address the customer provided to you. This could include a copy of the shipment receipt, shipping label, etc. It should show the customer's full shipping address, if possible.

The tracking number for a physical product, obtained from the delivery service. If multiple tracking numbers were generated for this purchase, please separate them with commas.

(ID of a file upload) Any additional evidence or statements.

Any additional evidence or statements.

Date by which evidence must be submitted in order to successfully challenge dispute. Will be 0 if the customer's bank or credit card company doesn't allow a response for this particular dispute.

Whether evidence has been staged for this dispute.

Whether the last evidence submission was submitted past the due date. Defaults to false if no evidence submissions have occurred. If true, then delivery of the latest evidence is *not* guaranteed.

The number of times evidence has been submitted. Typically, you may only submit evidence once.

Payment method type.