java.lang.Object | |
↳ | com.wsl.modules.stripe.client.StripeChargeClient |
Encapsulates Charge-related Stripe API calls.
Public Constructors | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Public Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Capture a Charge
| |||||||||||
Create a Charge
| |||||||||||
List all Charges
| |||||||||||
Retrieve a Charge
| |||||||||||
Update a Charge
Updates the specified charge by setting the values of the parameters passed.
|
[Expand]
Inherited Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
From class
java.lang.Object
|
Capture a Charge
id | The id of the charge to capture |
---|---|
amount | The amount to capture, which must be less than or equal to the original amount. Any additional amount will be automatically refunded. |
applicationFee | An application fee to add on to this charge. Can only be used with Stripe Connect. |
statementDescriptor | An arbitrary string to be displayed on your customer's credit card statement. This may be up to 22 characters. As an example, if your website is RunClub and the item you're charging for is a race ticket, you may want to specify a statement_descriptor of RunClub 5K race ticket. The statement description may not include <>"' characters, and will appear on your customer's statement in capital letters. Non-ASCII characters are automatically stripped. While most banks display this information consistently, some may display it incorrectly or not at all. |
receiptEmail | The email the receipt should be sent to |
StripeConnectorException | when there is a problem with the Connector |
---|
Create a Charge
amount | A positive integer in the smallest currency unit (e.g 100 cents to charge $1.00, or 1 to charge ¥1, a 0-decimal currency) representing how much to charge the card. The minimum amount is $0.50 (or equivalent in charge currency). |
---|---|
currency | 3-letter ISO code for currency |
customerId | The ID of an existing customer that will be charged in this request. either source or customer is required |
source | A payment source to be charged, such as a credit card. If you also pass a customer ID, the source must be the ID of a source belonging to the customer. Otherwise, if you do not pass a customer ID, the source you provide must be a Map containing a user's credit card details. Although not all information is required, the extra info helps prevent fraud. |
description | An arbitrary string which you can attach to a charge object. It is displayed when in the web interface alongside the charge. Note that if you use Stripe to send automatic email receipts to your customers, your receipt emails will include the description of the charge(s) that they are describing. |
metadata | A set of key/value pairs that you can attach to a charge object. It can be useful for storing additional information about the customer in a structured format. It's often a good idea to store an email address in metadata for tracking later. |
capture | Whether or not to immediately capture the charge. When false, the charge issues an authorization (or pre-authorization), and will need to be captured later. Uncaptured charges expire in 7 days. For more information, see authorizing charges and settling later. |
statementDescriptor | An arbitrary string to be displayed on your customer's credit card statement. This may be up to 22 characters. As an example, if your website is RunClub and the item you're charging for is a race ticket, you may want to specify a statement_descriptor of RunClub 5K race ticket. The statement description may not include <>"' characters, and will appear on your customer's statement in capital letters. Non-ASCII characters are automatically stripped. While most banks display this information consistently, some may display it incorrectly or not at all. |
receiptEmail | The email address to send this charge's receipt to. The receipt will not be sent until the charge is paid. If this charge is for a customer, the email address specified here will override the customer's email address. Receipts will not be sent for test mode charges. If receipt_email is specified for a charge in live mode, a receipt will be sent regardless of your email settings. |
destination | An account to make the charge on behalf of. If specified, the charge will be attributed to the destination account for tax reporting, and the funds from the charge will be transferred to the destination account. The ID of the resulting transfer will be returned in the transfer field of the response. See the documentation for details. |
applicationFee | A fee in cents that will be applied to the charge and transferred to the application owner's Stripe account. To use an application fee, the request must be made on behalf of another account, using the Stripe-Account header, an OAuth key, or the destination parameter. For more information, see the application fees documentation. |
shipping | Shipping information for the charge. Helps prevent fraud on charges for physical goods. |
StripeConnectorException | when there is a problem with the Connector |
---|
List all Charges
createdTimestamp | A filter on the list based on the object created field. The value can be a string with an integer Unix timestamp, |
---|---|
created | ... or it can be a dictionary with the following options: gt, gte, lt, lte |
customer | Only return charges for the customer specified by this customer ID. |
endingBefore | A cursor for use in pagination. ending_before is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, starting with obj_bar, your subsequent call can include ending_before=obj_bar in order to fetch the previous page of the list. |
limit | A limit on the number of objects to be returned. Limit can range between 1 and 100 items. |
startingAfter | A cursor for use in pagination. starting_after is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, ending with obj_foo, your subsequent call can include starting_after=obj_foo in order to fetch the next page of the list. |
StripeConnectorException | when there is a problem with the Connector |
---|
Retrieve a Charge
id | The identifier of the charge to be retrieved. |
---|
StripeConnectorException | when there is a problem with the Connector |
---|
Update a Charge Updates the specified charge by setting the values of the parameters passed. Any parameters not provided will be left unchanged. This request accepts only the description, metadata, receipt_emailand fraud_details as arguments.
id | The id of the charge to update |
---|---|
description | An arbitrary string which you can attach to a charge object. It is displayed when in the web interface alongside the charge. Note that if you use Stripe to send automatic email receipts to your customers, your receipt emails will include the description of the charge(s) that they are describing. |
metadata | A set of key/value pairs that you can attach to a charge object. It can be useful for storing additional information about the customer in a structured format. It's often a good idea to store an email address in metadata for tracking later. |
receiptEmail | The email address to send this charge's receipt to. The receipt will not be sent until the charge is paid. If this charge is for a customer, the email address specified here will override the customer's email address. Receipts will not be sent for test mode charges. If receipt_email is specified for a charge in live mode, a receipt will be sent regardless of your email settings. |
fraudDetails | A set of key/value pairs you can attach to a charge giving information about its riskiness. If you believe a charge is fraudulent, include a user_report key with a value of fraudulent. If you believe a charge is safe, include a user_report key with a value of safe. Note that you must refund a charge before setting the user_report to fraudulent. Stripe will use the information you send to improve our fraud detection algorithms. |
StripeConnectorException | when there is a problem with the Connector |
---|