Returns a list of CreditReversals.
Parameters
- financial_
accountstring Returns objects associated with this FinancialAccount.
- received_
creditstring Only return CreditReversals for the ReceivedCredit ID.
- statusenum
Only return CreditReversals for a given status.
Possible enum valuescanceledThe CreditReversal has been canceled before it has been sent to the network and no funds have left the account. (Currently not supported).
postedThe CreditReversal has been sent to the network and funds have left the account (with the Transaction posting)
processingThe CreditReversal starting state. Funds are “held” by a pending Transaction (but they are still part of the current balance).
More parameters
- ending_
beforestring - limitinteger
- starting_
afterstring
Returns
A dictionary with a data property that contains an array of up to limit CreditReversals, starting after CreditReversal starting_. Each entry in the array is a separate CreditReversal object. If no more CreditReversal are available, the resulting array will be empty.
{ "object": "list", "url": "/v1/treasury/credit_reversals", "has_more": false, "data": [ { "id": "credrev_1Mtklw2eZvKYlo2CJG2MWJM7", "object": "treasury.credit_reversal", "amount": 1000, "created": 1680756608, "currency": "usd", "financial_account": "fa_1Mtklw2eZvKYlo2CNHscZzs2", "hosted_regulatory_receipt_url": "https://payments.stripe.com/regulatory-receipt/CBQaFwoVYWNjdF8xMDMyRDgyZVp2S1lsbzJDKICfuaEGMgYv0T_PcXU6NpP_n6wAfI9LKta3LkDRNQT8oLGdQf7JcXsskGjrq1LICpYVy5a3oOBI5gaVvTy8MtwpT1PTpQ", "livemode": false, "metadata": {}, "network": "ach", "received_credit": "rc_1Mtklw2eZvKYlo2CxuluQFPR", "status": "processing", "status_transitions": { "posted_at": null }, "transaction": "trxn_1Mtklw2eZvKYlo2CKkbNA2TS" } ]}You can reverse some ReceivedDebits depending on their network and source flow. Reversing a ReceivedDebit leads to the creation of a new object known as a DebitReversal.
A Payment Record is a resource that allows you to represent payments that occur on- or off-Stripe. For example, you can create a Payment Record to model a payment made on a different payment processor, in order to mark an Invoice as paid and a Subscription as active. Payment Records consist of one or more Payment Attempt Records, which represent individual attempts made on a payment network.
- GET/
A Payment Attempt Record represents an individual attempt at making a payment, on or off Stripe. Each payment attempt tries to collect a fixed amount of money from a fixed customer and payment method. Payment Attempt Records are attached to Payment Records. Only one attempt per Payment Record can have guaranteed funds.
A feature represents a monetizable ability or functionality in your system. Features can be assigned to products, and when those products are purchased, Stripe will create an entitlement to the feature for the purchasing customer.