The identifier of payment provider contract you want to process the transaction request with.

Flags a payment request for either pre-authorization or final authorization.

• PRE_AUTH is used when the authorized amount is unknown and can be adjusted later.

• FINAL_AUTH is used when a final authorized amount is known and the transaction will definitely be captured in whole.

The ID of a customer.

Optional. The invoice number to track this payment.

A reference specified by the merchant to identify the transaction.

Determines the sales channel the shopper gives their card details through:

• ECOMMERCE Online transactions where the cardholder is present.

• MAIL order transactions where the shopper is in contact with the merchant via email.

• TELEPHONE order transactions where the shopper is in contact with the merchant via telephone.

The full user agent string of the device the customer used to submit the transaction.

A reference used by the merchant to typically capture a description of the service provided. It could then be used by the merchant to help locate transactions. One could envision a situation where a merchant is trying to locate a transaction/ receipt but in speaking with the customer, the only (or at least a predominant) detail is what service was rendered

Use this field to request your transaction to be exempted from the application of the Strong Customer Authentication (SCA). Be advised that the use of this field may result to your liability in case of fraudulent transaction.

Possible Values:

1 - Low value payment

2 - Acquirer Transaction Risk Analysis

3 - Trusted beneficiary exemption

4 - Secure Corporate Payment (SCP) exemption

5 - Merchant Initiated Transaction

6 - SCA Delegation

Three-letter ISO 4217 alphabetical currency code. Supported values are: AUD

Represents a Card type or brand. It should correspond to a consistent name, the list of standard names is as follows:

An indicator to show under which terms the credit was provided.

The cardholder data encrypted using the OnlinePay provided public key. This can be obtained using either Verifone.JS solution or OnlinePay Checkout in capture mode.

The data to encrypt is a JSON with possible tags being cardNumber, sequenceNumber, cardholderName, startMonth, startYear, expiryMonth, expiryYear, cvv. This should be a single JSON line and should not contain any spaces. Read Secure card capture key for details.

Additionally, a tag called captureTime must be presenting indicating the time the card was captured in UTC in format RFC 3339, section 5.6. eg. 2019-08-24T14:15:22Z. Encrypted card is valid for only 15 minutes.

The SVC Access Code encrypted using the OnlinePay provided public key. This can be obtained using either Verifone.JS solution or OnlinePay Checkout in capture mode.

The data to encrypt is a JSON with tag svcAccessCode.

Additionally a tag called captureTime must be presenting indicating the time the cvv was captured in UTC in format RFC 3339, section 5.6. eg. 2019-08-24T14:15:22Z.

The alias for the public key used to encrypt this card.

A code defined by the merchant that affects the calculation of the total amount.

This field indicates the taxable status of the transaction (if any of the purchased items are taxable). This field is part of so-called Level 2 data. If the value TAX_PROVIDED is sent, tax_amount should also be provided