Process a card sale
A sale combines authorization and capture in one transaction. Use it when purchases are fulfilled immediately, such as retail or e-commerce checkout. If the issuing bank approves, an approval code is returned; if it declines, the response includes the decline reason.
Authorizations
Basic authentication header of the form Basic <encoded-value>, where <encoded-value> is the base64-encoded string username:password.
Body
API support various types of use. Required fields are defined by the most basic call. For other uses be sure to send the required information defined in the schema and examples.
Unique identifier of the submerchant.
The amount to charge.
The payment credential to charge: a one-time token from the web component or a stored Jupico token.
True when the cardholder actively initiates the payment; false for merchant-initiated transactions such as recurring charges.
Line items included in the total amount.
Free-text description of the transaction.
The total amount of sales tax must be between: Visa: 0.1% - 18% MasterCard: 0.1% - 23% Default: 0.1% - 50%
When true, the sales tax portion is withheld from the merchant's settlement until released.
Fee added to the transaction at processing time and itemized separately.
Card verification code (CVV/CVC).
Your own reference for this transaction. Returned in responses and query results for reconciliation.
Billing contact and address details for the payer.
Shipping contact and address details for the order.
metadata is an object that can host as much as 50 key-value pairs, where the keys can be at most 40 char length and can’t include the characters “[“ or “]”, and the values must be strings and cannot exceed 500 chars Learn more about metadata
Overrides the descriptor that appears on the cardholder's statement.
Response
Successful sale

