Loads the payment method.

The type of load you are trying to do, when absent we default to 'load'

The merchant account identifier, with which you want to process the transaction.

The reference to uniquely identify a payment. This reference is used in all communication with you about the payment status. We recommend using a unique value per payment; however, it is not a requirement. If you need to provide multiple references for a transaction, separate them with hyphens ("-"). Maximum length: 80 characters.

Specifies the sales channel, through which the shopper gives their card details, and whether the shopper is a returning customer. For the web service API, Adyen assumes Ecommerce shopper interaction by default.

This field has the following possible values:

• Ecommerce - Online transactions where the cardholder is present (online). For better authorisation rates, we recommend sending the card security code (CSC) along with the request.
• ContAuth - Card on file and/or subscription transactions, where the cardholder is known to the merchant (returning customer). If the shopper is present (online), you can supply also the CSC to improve authorisation (one-click payment).
• Moto - Mail-order and telephone-order transactions where the shopper is in contact with the merchant via email or telephone.
• POS - Point-of-sale transactions where the shopper is physically present to make a payment using a secure payment terminal.

The physical store, for which this payment is processed.

Authorisation code:

• When the payment is authorised, this field holds the authorisation code for the payment.
• When the payment is not authorised, this field is empty.

Adyen's 16-character string reference associated with the transaction/request. This value is globally unique; quote it when communicating with us about this request.

If the transaction is refused or an error occurs, this field holds Adyen's mapped reason for the refusal or a description of the error.

When a transaction fails, the authorisation response includes resultCode and refusalReason values.

The result of the payment. Possible values:

• Success – The operation has been completed successfully.
• Refused – The operation was refused. The reason is given in the refusalReason field.
• Error – There was an error when the operation was processed. The reason is given in the refusalReason field.
• NotEnoughBalance – The amount on the payment method is lower than the amount given in the request. Only applicable to balance checks.

Raw refusal reason received from the third party, where available