Skip to content
This repository was archived by the owner on Apr 23, 2021. It is now read-only.

Files

Latest commit

fcb6006 · Nov 20, 2019

History

History
28 lines (21 loc) · 4.46 KB

ChargeRequest.md

File metadata and controls

28 lines (21 loc) · 4.46 KB

ChargeRequest

Description

Defines the parameters that can be included in the body of a request to the Charge endpoint. Deprecated - recommend using CreatePayment Note: This model is deprecated.

Properties

Name Type Description Notes
idempotencyKey String A value you specify that uniquely identifies this transaction among transactions you've created. If you're unsure whether a particular transaction succeeded, you can reattempt it with the same idempotency key without worrying about double-charging the buyer. See Idempotency keys for more information.
amountMoney Money The amount of money to charge. Note that you specify the amount in the smallest denomination of the applicable currency. For example, US dollar amounts are specified in cents. See Working with monetary amounts for details. The value of `currency` must match the currency associated with the business that is charging the card.
cardNonce String A nonce generated from the `SqPaymentForm` that represents the card to charge. The application that provides a nonce to this endpoint must be the same application that generated the nonce with the `SqPaymentForm`. Otherwise, the nonce is invalid. Do not provide a value for this field if you provide a value for `customer_card_id`. [optional]
customerCardId String The ID of the customer card on file to charge. Do not provide a value for this field if you provide a value for `card_nonce`. If you provide this value, you must also provide a value for `customer_id`. [optional]
delayCapture Boolean If `true`, the request will only perform an Auth on the provided card. You can then later perform either a Capture (with the `CaptureTransaction` or a Void (with the `VoidTransaction`. Default value: `false` [optional]
referenceId String An optional ID you can associate with the transaction for your own purposes (such as to associate the transaction with an entity ID in your own database). This value cannot exceed 40 characters. [optional]
note String An optional note to associate with the transaction. This value cannot exceed 60 characters. [optional]
customerId String The ID of the customer to associate this transaction with. This field is required if you provide a value for `customer_card_id`, and optional otherwise. [optional]
billingAddress Address The buyer's billing address. This value is optional, but this transaction is ineligible for chargeback protection if neither this parameter nor `shipping_address` is provided. [optional]
shippingAddress Address The buyer's shipping address, if available. This value is optional, but this transaction is ineligible for chargeback protection if neither this parameter nor `billing_address` is provided. [optional]
buyerEmailAddress String The buyer's email address, if available. This value is optional, but this transaction is ineligible for chargeback protection if it is not provided. [optional]
orderId String The ID of the order to associate with this transaction. If you provide this value, the `amount_money` value of your request must exactly match the value of the order's `total_money` field. [optional]
additionalRecipients List<AdditionalRecipient> The basic primitive of multi-party transaction. The value is optional. The transaction facilitated by you can be split from here. If you provide this value, the `amount_money` value in your additional_recipients must not be more than 90% of the `amount_money` value in the charge request. The `location_id` must be the valid location of the app owner merchant. This field requires the `PAYMENTS_WRITE_ADDITIONAL_RECIPIENTS` OAuth permission. This field is currently not supported in sandbox. [optional]
verificationToken String A token generated by SqPaymentForm's verifyBuyer() that represents customer's device info and 3ds challenge result. [optional]