Docs

Create Charge

To charge a Customer credit card, you first need to create a charge object.

POST

Query

Field selectionChoose which fields should be included in the response. Learn more
string

Comma-separated response fields to include.

Body

Arguments
string

Conditionally required. The unique identifier for the card object.

boolean

Flag that indicates if the charge was made from a mobile device. The card can be keyed, swiped, dipped or tapped on the merchant's POS device.

object
string

Preferred to specifying card or cardOnFile in order to ensure PCI compliance. Opaque representation of the credit card or debit card associated with this charge, as returned by the token endpoint. Applications that access cardholder information using the Payments API are required to follow the payment application data security standard (PA DSS) established by the payment card industry, which specifies how cardholder data must be protected. As such, the token resource provides a programatic way to comply with this standard without having to hold sensitive card information on your own servers.

object
string

The type of credit or debit card. Valid values include the values available in the list dropdown.

boolean

Flag that indicates if the charge is an eCommerce transaction made over the web.

string
stringrequired

Three-letter ISO 4217 currency code representing the currency in which the charge was made.

stringrequired

Amount of the transaction. Valid values range 0.00 through 99999.99.

object

Additional data you wish to store for this transaction.

Every app you connect,one REST pattern

Call any app with one REST pattern. MindCloud handles each provider's auth, request shape, and responses for you.

Learn what the Universal API is
One REST patternUse the same request structure across apps like Slack, HubSpot, Salesforce, and thousands more.
Managed connectionsSend a MindCloud connection ID instead of handling provider tokens, refresh logic, and credential storage yourself.
Action-level docsEach action page shows the exact endpoint, required arguments, optional controls, and response behavior for that app version.