Create, update, and query the available Charges in Stripe.
Table Specific InformationIn this table only select, insert, and update operations are allowed.
Server-Side Query Support
The connector will use the Stripe API to filter the results by the following columns and operators while the rest of the filter is executed client side within the connector.
- Id, Currency, CustomerId, Created, Source support the following operators:<,>>=, <, <=, =.
The provider supports all columns to be used as criteria in the Where clause of Select statement, as long as SupportEnhancedSQL is set to True. If SupportEnhancedSQL property is set to False, you still can retreive:
-a Charge by specifying its Id:
SELECT * FROM Charges WHERE Id='ch_12345678'
-Charges that belong to a Customer:
SELECT * FROM Charges WHERE CustomerId='cus_12345678'
-Charges created after a specific date (Created may be used with the >, >=, <, <=, or = conditions and may be used twice to specify a range):
SELECT * FROM Charges WHERE Created > '2016-01-03'
Amount, Currency and Customer or Source columns are required to charge a credit card.
INSERT INTO Charges (Amount, Currency, CustomerId) VALUES (2000, 'usd', 'cus_12345678')
To modify a Charge, provide an Id.
UPDATE Charges SET Description='updated charge' WHERE Id='ch_17rPMOATXQzBWNrliIRnfI5B'
Delete is not supported.
The Id of the charge.
The amount of the charge.
The currency of the charge.
The customer Id of the charge.
The amount in cents refunded.
The application fee (if any) for the charge.
The amount of the application fee (if any) for the charge.
The Id of the balance transaction that describes the impact of this charge on your account balance .
Billing information associated with the payment method at the time of the transaction.
Whether the charge was created without capturing.
The full statement descriptor that is passed to card networks, and that is displayed on your customers' credit card and bank statements. Allows you to see what the statement descriptor looks like after the static and dynamic portions are combined.
The datetime the charge was created.
The description of the charge.
The account (if any) the charge was made on behalf of.
Whether the charge has been disputed.
The details about the dispute if the charge has been disputed.
The error code explaining the reason for the charge failure if available.
The message to the user further explaining the reason for the charge failure if available.
Information on fraud assessments for the charge.
The Id of the invoice this charge is for if one exists.
Whether the charge is in live mode.
The charge metadata object.
The Id of the order this charge is for if one exists.
Details about whether the payment was accepted, and why. See understanding declines for details.
If the charge succeeded or was successfully authorized for later capture.
ID of the PaymentIntent associated with this charge, if one exists.
ID of the payment method used in this charge.
Details about the payment method at the time of the transaction.
The email address that the receipt for this charge was sent to.
The transaction number that appears on email receipts sent for this charge.
This is the URL to view the receipt for this charge. The receipt is kept up-to-date to the latest state of the charge, including any refunds. If the charge is for an Invoice, the receipt will be stylized as an Invoice receipt.
Whether or not the charge has been fully refunded.
The list of refunds that have been applied to the charge.
ID of the review associated with this charge if one exists.
Shipping information for the charge.
The source of every charge is a credit or debit card.
The transfer Id that created this charge.
The extra information about a charge.
The status of the payment is either succeeded, pending, or failed.
The Id of the transfer to the destination account.
An optional dictionary including the account to automatically transfer to as part of a destination charge.
A string that identifies this transaction as part of a group.
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
The Id of the connected account to get charges for