LowCodeAPI
55 APIs
  • Charges(6)
    • POST
      Create a charge
    • GET
      List all charges
    • GET
      Retrieve a charge
    • POST
      Update a charge
    • POST
      Capture a charge
    • GET
      Search charges
POST
GET
GET
POST
POST
GET
POST
https://api.lowcodeapi.com/stripe/v1/charges
Request Payload

The payload will be sent as a application/json as a part of the request body.

Payload
amountnumber*
Amount intended to be collected by this payment. A positive integer representing how much to charge in the smallest currency unit (e.g. 100 cents to charge $1.00 or 100 to charge ¥100 a zero-decimal currency). The minimum amount is $0.50 US or equivalent in charge currency. The amount value supports up to eight digits (e.g. a value of 99999999 for a USD charge of $999999.99)
currencystring*
Three-letter ISO currency code; in lowercase. Must be a supported currency customer
descriptionstring
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
metadataobject
Set of key-value pairs that you can attach to an object. This can be useful for storing additional information about the object in a structured format. Individual keys can be unset by posting an empty value to them. All keys can be unset by posting an empty value to metadata
receipt_emailstring
The email address to which this charge’s receipt will be sent. The receipt will not be sent until the charge is paid; and no receipts will be sent for test mode charges. If this charge is for a Customer; the email address specified here will override the customer’s email address. If receipt_email is specified for a charge in live mode; a receipt will be sent regardless of your email settings
shippingstring
Shipping information for the charge. Helps prevent fraud on charges for physical goods
sourcestring
A payment source to be charged. This can be the ID of a card (i.e. credit or debit card); a bank account; a source; a token; or a connected account. For certain sources—namely; cards; bank accounts; and attached sources—you must also pass the ID of the associated customer
statement_descriptorstring
For card charges use statement_descriptor_suffix instead. Otherwise; you can use this value as the complete description of a charge on your customers’ statements. Must contain at least one letter; maximum 22 characters'
statement_descriptor_suffixstring
Provides information about the charge that customers see on their statements. Concatenated with the prefix (shortened descriptor) or statement descriptor that’s set on the account to form the complete statement descriptor. Maximum 22 characters for the concatenated descriptor.
Response
API response data will be shown here once the request is completed.
Stripe