--- title: "paymentMethod" method: POST path: "/paymentMethod" --- # paymentMethod `POST /paymentMethod` ## Headers - `Authorization` string, required - `Content-type` string, required - `DateTime` string, required - `KeyID` string, required - `MsgID` string - `SignType` string, required - `Idempotency-Key` string ## Request body - object - `merchantTransInfo` object, required — This is the information for merchant to identify this Transaction Usage Instruction For each new POST request, including PaymentMethod, Payment, Capture, Cancel, Refund, CancelOrRefund, DataSubmission and DeviceBinding, a new and unique merchantTranInfo shall be assigned for the transaction - `merchantTransID` string — The merchant assigned transaction identifier, should be unique under same Store ID. Usage Instruction 1.Field type: String(32) - `merchantOrderReference` string — The merchant assigned Oder Reference Number. Usage Instruction 1.Evonet does not validate this value. Merchant can define this reference number to track different transactions related to the same order within merchant site. 2.Field type: String(32) - `merchantTransTime` string, date-time, required — Time when merchant submits this transaction Usage Instruction 1.Field type: Datetime 2.Format: ISO 8601 YYYY-MM-DDThh:mm:ssTZD 3.Sample: 2017-07-17T13:42:40+01:00 - `transAmount` object — This is used to define the amount for the transaction - Usage Instruction 1. Used in POST Payment request, to send the payment transaction amount 2. Used in POST Capture request, to send the capture amount 3. Used in POST Refund request, to send the refund transaction amount 4. Used within object payment, capture or refund in the response or notification from Evonet, to specify the corresponding amount of the objects. 5. Used in POST PaymentMethod, to indicate currency for this transaction when the store is assigned multiple currencies in Evonet. If the store is not assigned multiple currencies, this object will be ignored. - `currency` string, required — The currency for this transaction. - Value defined The three-character currency code as defined in ISO-4217. For example : HKD - Usage Instruction: 1. Field Type: String(3) - `allowAuthentication` boolean — This is to indicate if this Payment or Payment Method needs to conduct authentication - Usage instruction: 1. In Evonet, each merchant is configured with Non-Authentication, Optional-Authentication and Must-Authentication. When store is configured Optional-Authentication, this field is applied. 2. This filed is used in POST Payment request and Payment Method request, if true, Evonet will conduct additional authentication for this transaction or tokenize. 3. If not present, means default value=false, Evonet will not conduct authentication process for this transaction 4. Only used when paymentMethod.type=card 5. In Payment request, when paymentMethod.type=card and authenticationOnly=true this field is not applied. 6. Field Type: boolean - `returnURL` string — This is the URL address provided by merchant. After completing the authentication or payment processing, the user is redirected back to the merchant site. This URL address specifies which merchant site page the user goes back to. - Usage Instruction 1. Required in POST PaymentMethod or POST Payment request message when 3DS authentication is being performed. 2. Required in POST PaymentMethod request message when performing the tokenization with Alipay. 3. Required in POST Payment request message when performing the payment with E-Wallets, points and onlineBanking including: 3.1 Alipay, Alipay+ and Jkopay on PC WEB 3.2 Alipay, Alipay+, Alipay HK, WeChat Pay and Jkopay on Mobile WAP 3.3 WeChat Pay in Official Account 3.4 SecurePay for UnionPay, TrueMoney Wallet, Rabbit LINE Pay, Pay with Points, Krungsri Online, Bualuang iBanking, Boost, MCash, ShopeePay, Touch 'N Go eWallet, Cards_KOR, Naver_Pay, Kakao_Pay and PAYCO, DANA, OVO, ShopeePay Indonesia, Akulaku, BNI VA, BRI VA, CIMB VA, Mandiri VA, Maybank VA, Permata VA, au, SoftBank, NTT Docomo, LINE Pay, Merpay, Paypay, Rakuten Pay, BC_Card, Kookmin_Bank_Card, Hana_Bank_Card, Samsung_Card, Shinhan_Bank_Card, Hyundai_Card, Lotte_Card or Nonghyup_Bank_Card on PC WEB, Mobile WAP and wallet APP. 3.5 K PLUS on Mobile WAP and wallet APP. 3.6 SCB Easy Net on wallet APP 4. Field Type: String(300) 4.1 When authentication.type=threeDSIntegrator or threeDSPage, the maximum is 75. 4.2 When Payment Brand is Alipay or AlipayHK, the maximum is 200. 5. The format of the webhook must contain http:// or htps:// - `paymentMethod` object, required — This field includes the Payment Method information, including Payment Method selected by User for Payment, and the Payment Method supported by the merchant - `recurringProcessingModel` 'Subscription' | 'Unscheduled' | 'COF' — This is to indicate whether a transaction is a recurring or COF transaction. - Usage Instruction 1. Field Type: String(20) 2. For Google Pay’s recurring payment, only support Subscription and Unscheduled. - `isFirstCITTxn` boolean — For special scenarios, ASI can be used as the first CIT for Recurring. - Value definition true: This is first CIT transaction with saving credentials for recurring transaction. false: This is transaction with saving credentials, but not the CIT transaction for recurring transaction. - Usage Instruction 1. Applies only to Payment with amount 0 or PaymentMethod. 2. Ignore this field if it appears when Payment with amount is not 0. Notes: 1. Approval rate of ASI and Payment after ASI, is subjected to issuers 2. If there is chargeback for Payment after ASI, liability in on merchant. 3. For Google Pay‘s’ recurring binding card, only support isFirstCITTxn=true. - `type` 'card' | 'e-wallet' | 'token' | 'points' | 'onlineBanking' | 'bankTransfer' | 'buyNowPayLater' | 'carrierBilling' | 'cash' | 'prepaidCard' | 'GooglePay', required — This field is to indicate the type of payment method for this transaction: - Usage Instruction: 1. For POST PaymentMethod, only card and E-Wallet are applied 2. For POST Payment, all the values are applied 3. Field Type: String(32) - `accountUpdateIndicator` 'Y' — Account Update Indicator - Usage Instruction 1. This field is suitable for the paymentBrand=Visa - `card` object — This field is to send card related information for this transaction -Usage Instruction: 1. For POST Payment or POST PaymentMethod. If paymentMethod.type = card, the field must be present 2. For PUT PaymentMethod. Merchant may send this field to update the card information corresponding to the token. 3. Evonet may include this object in response 4. For POST Payment or POST PaymentMethod response. If paymentMethod.type=GooglePay & The paymentMethod.encryptedData is a card that consists of PAN, the field will be present. - `encryptedCardInfo` string — The encrypted card information. -Usage Instruction: 1. If merchant has not completed PCI DSS compliance certification, merchant shall send card information in this field, without storing card information in system. Evonet also provide SDK for merchant to simplify this process. Merchant shall choose the solution upon to acquirer's requirement or contract. 2. Please refer to Payment in Evonet API Integration Guide for detailed information about the requirement and steps for the encryption. 3. When both of paymentMethod.card.cardInfo and paymentMethod.card.encryptedCardInfo present, the paymentMethod.card.cardInfo will be applied. 4. For PUT PaymentMethod request, this field is used to update token. 5. Field Type: String(2048) - `cardInfo` object — The card information structure for transmitting card information in plain text. -Usage Instruction: 1. If merchant has completed PCI DSS compliance certification, merchant can send card information in this field. 2. When both of paymentMethod.card.cardInfo and paymentMethod.card.encryptedCardInfo present, the paymentMethod.card.cardInfo will be applied. 3. For PUT PaymentMethod request, this field is used to update token - `cardNumber` string, required — The card number - Usage Instruction 1. If cardInfo Object presents, this field must be present 2. Field Type: String(19) - `expiryDate` string — The expiration date of the card -Usage Instruction 1. Format: MMYY 2. Not applied for some UnionPay or TPN debit card transactions. 3. For PUT PaymentMethod request, this field is used to update token. 4. Field Type: Fixed length, String(4) - `cvc` string — The security code on the back of card -Usage Instruction 1. Field Type: String(4) - `holderName` string — The cardholder's name. - Usage Instruction 1. Field Type: String(50) - `tokenValidDays` '1~365' | '0' | 'not presnet' — The validity days defined by merchant for the User token - Usage Instruction 1. For POST PaymentMethod and POST Payment, 0 and not present mean permanent valid 2. For PUT PaymentMethod, 0 means permanent valid, not present means not update 3. For PUT PaymentMethod, 1~365 means renew the vailed time to the date of request date + 1～365 day(s) 4. Field Type: String(3) - `vaultID` string — The group ID which the token belongs to. This token is unique under same vault ID - Usage Instruction: 1. This ID is assigned in Evonet, and will be provided to customer before integration. 2. This field is mandatory when Evonet needs to generate token, which is as the reference for the token. 3. For POST PaymentMethod, this field must be present 4. For POST Payment, if paymentMethod.type.card.tokenize=true, this field must be present 5. Field Type: String(36) - `e-wallet` object — This is used to send E-Wallet related Information for this transaction - Usage Instruction 1. For POST payment or PaymentMethod request, if paymentMethod.type = ‘e-wallet’, the field must be present 2. Evonet may include this object in response - `paymentBrand` 'Alipay' | 'Alipayplus' | 'WeChat_Pay' | 'DANA', required — This is to indicate the payment brand of E-Wallet. - Value defined The accepted values of this field, please refer to e-wallet paymentMethod type of the Appendix 8.8 payment brands - Usage Instruction 1. For POST PaymentMethod request: only Alipay, Alipayplus, AlipayHK, Boost, DANA, GCash, Kakao_Pay, Rabbit_LINE_Pay, TNG, TrueMoney_Wallet, Maya, Naver_Pay, GrabPay_SGP and WeChat_Pay are applied 2. For POST Payment request: all values are applied 3. All values are applied in response from Evonet 4. This field is optional when transInitiator.inStorePaymentScenario=CPM 5. Field Type: String(32) - `vaultID` string — The group ID which the token belongs to. This token is unique under same vault ID - Usage Instruction: 1. This ID is assigned in Evonet, and will be provided to customer before integration. 2. This field is mandatory when Evonet needs to generate token, which is as the reference for the token. 3. For POST PaymentMethod, this field must be present 4. Field Type: String(36) - `planID` string — This is the ID assigned by WeChat, when merchant obtained the license for some special service like Recurring Payment from WeChat - Usage Instruction 1. Merchant shall obtain the license and the ID from WeChat before starting the service 2. For POST PaymentMethod, this field must be present when paymentMethod.e-wallet.paymentBrand=WeChat_Pay 3. Field Type: String(1024) - `subOpenID` string — This is the user ID for a User in merchant's Mini-Program of WeChat - Usage Instruction 1. After user logins in merchant's Mini-Program of WeChat, merchant could have this ID for user 2. For POST Payment, it is mandatory when the paymentMethod.e-wallet.paymentBrand = WeChat_Pay, and transInitiator.platform=MINI. 3. For POST PaymentMethod, this is mandatory when paymentMethod.e-wallet.paymetBrand=WeChat_Pay 4. Field Type: String(64) - `buyNowPayLater` object — This field is to send Buy Now Pay Later payment related information for this transaction -Usage Instruction: 1. For POST Payment. If paymentMethod.type = buyNowPayLater, the field must be present 2. Evonet may include this object in response - `paymentBrand` string, required — This is to indicate the payment brand of Buy Now Pay Later. - Value defined The accepted values of this field, please refer to buyNowPayLater paymentMethod type of the Appendix 8.8 payment brands - Usage Instruction 1. For POST Payment request: all values are applied 2. All values are applied in response from Evonet 3. Field Type: String(32) - `vaultID` string — The group ID which the token belongs to. This token is unique under same vault ID - Usage Instruction: 1. This ID is assigned in Evonet, and will be provided to customer before integration. 2. Evonet may include this field in response 3. Field Type: String(36) - `googlePay` object — This field is to send Google Pay-related information for this transaction -Usage Instruction: 1. For POST Payment or POST PaymentMethod. If paymentMethod.type = GooglePay, the field must be present. - `encryptedData` string, required — The Google Pay API returns payment methods in a signed and encrypted PaymentMethodToken payload. The returned payment methods are either cards that consist of PAN, or tokenized cards that consist of device PAN and cryptograms. The message returned by Google in the PaymentData response is a UTF-8 encoded, serialized JSON object - Usage Instruction 1. If googlePay Object is present, this field must be present. 2. It gets value from Google Pay API's response-paymentData.paymentMethodData.tokenizationData.token field. 3. Field Type: String(5000). - `paymentBrand` 'Visa' | 'Mastercard', required — This is used to indicate the card scheme which the card belongs to. - Usage Instruction 1. If googlePay Object is present, this field must be present. 2. It gets value from Google Pay API's response-paymentData.paymentMethodData.tokenizationData.token field 3. Field Type: String(32). - `tokenize` boolean — This is used for merchant to indicate whether need to generate token after Payment completed. - Value definition true: use the card information and generate the token. false: do not need to generate a token -Usage Instruction 1. This field is used in POST Payment only. 2. If not present, means default value = false, Evonet will not generate a token for this transaction. 3. If you send the tokenize = true in the POST Payment message, but there is no token object in the response, that means the tokenization is failed. - `vaultID` string — The group ID which the token belongs to. This token is unique under same vault ID - Usage Instruction: 1. This ID is assigned in Evonet, and will be provided to customer before integration. 2. This field is mandatory when Evonet needs to generate token, which is as the reference for the token. 3. For POST PaymentMethod, this field must be present 4. For POST Payment, if paymentMethod.type.googlePay.tokenize=true, this field must be present 5. For PUT PaymentMethod request, this field is used to update token 6. Field Type: String(36) - `tokenValidDays` '1~365' | '0' | 'not present' — The validity days defined by merchant for the User token. - Usage Instruction 1. For POST PaymentMethod and POST Payment, 0 and not present mean permanent valid. 2. For PUT PaymentMethod, 0 means permanent valid, not present means not update. 3. For PUT PaymentMethod, 1~365 means renewing the valid time to the date of request date + 1～365 day(s). 4. Field Type: String(3). - `authentication` object — The information used for User authentication with Card - Usage Instruction 1. Evonet supports securePlus and threeDS authentication types - `type` 'threeDSPage' | 'threeDSIntegrator' | ' FIDOPage' | 'threeDSPageOrFIDOPage' | 'threeDSIntegratorOrFIDOPage' — This is used for Evonet to response merchant which authentication type is applied for this transaction. - Usage Instruction: 1. In the request from merchant, only threeDSPage and threeDSIntegrator are applied 2. In the response from Evonet, all the values are applied. 3. If merchant is configured to support 3DS authentication in Evonet, merchant can send this field in the request of POST PaymentMethod and POST Payment, if not present, default value of threeDSPage is applied 4. If merchant is configured to support 3DS or SecurePlus authentication in Evonet, and authentication is performed, in the response of POST PaymentMerthod and POST Payment, Evonet will include this field to indicate the authentication type 5. In PUT Payment and PUT PaymentMethod request, the value in this field must be the same as POST request, if it is not presented, the default value is threeDSPage. 6. Field Type: String(20) - `merchantRiskIndicator` object — The merchant risk indicator for 3D Secure 2, which will be sent to authentication service provider - Usage Instruction 1. This is optional in Evonet 2. If merchant wants to send this information, please refer to Authentication Appendix for detail field definition - `threeDS` object — This field includes the related information for 3DS authentication - Usage Instruction 1. Merchant can use this object send challenge preference - `threeDSRequestorChallengeInd` '01' | '02' | '03' | '04' | '05' | '06' | '07' | '08' | '09' | '10' | '11' | '12' | '13' | '14' | '15-79' | '80-99' — Indicates whether a challenge is requested for this transaction. Note: If the element is not provided, the expected action is that the ACS would interpret as 01 = No preference. - `transInitiator` object, required — Information of terminal to initiate the transaction - Usage instruction 1. Used in the request of PaymentMethod, Payment. - `platform` 'WEB' | 'WAP' | 'APP' | 'MINI' | 'INWALLET' | 'POS', required — The type of terminal platform - Usage Instruction 1. When paymentMethod.onlineBanking.paymentBrand = K_PLUS, only WAP/APP/MINI/INWALLET are available in this field. 2. When paymentMethod.onlineBanking.paymentBrand=SCB_Easy_Net, only APP is available for this field. 3. When transInitiator.paymentScenario=inStore, only POS is available for this field. 4. When transInitiator.paymentScenario=EC or not present, only WEB, WAP, APP, MINI and INWALLET is available for this field. 5. Field Type: String(10) - `deviceType` 'Android' | 'iOS' — The terminal type: - Usage Instruction 1. In POST PaymentMethod, when paymentMethod.type=e-wallet or onlineBanking, platform=WAP/MINI/INWALLET/APP, this field must be present 2. In POST Payment, when paymentMethod.type=e-wallet, platform=APP, this field is applied. 3. Fired Type: String(20) - `deviceID` string — The ID of the client device. 1. Specify this parameter if you can obtain the information from the user. This helps Evonet laundering and fraud detection, and increases payment success rates. 2. Field Type: String (64) - `userRegion` string — The region of the user located - Usage Instruction: 1. Defined in ISO-3166-1 alpha-3. For example, HKG. 2. In POST PaymentMethod, when paymentMethod.e-wallet.paymentBrand=Alipayplus, this field is applied. 3. Field Type: String(3) - `osVersion` string — Operating system version. -Usage Instruction 1. In POST PaymentMethod, when paymentMethod.type=e-wallet, platform=WAP/MINI/INWALLET/APP, this field must be present 2. Field Type: String(20) - `userCreateIP` string, required — The IP address of the terminal where the user initiates the transaction -Usage Instruction 1. Mandatory when paymentMethod.e-wallet.paymentBrand = WeChat_Pay and transInitiator.platform = WAP. 2. Specify this parameter if you can obtain the information from the user. This helps Evonet laundering and fraud detection, and increases payment success rates. 3. Please use public IP address 4. When authentication.type is FIDOPage, threeDSPageOrFIDOPage or threeDSIntegratorOrFIDOPage,this field is mandatory. - `browserInfo` object — The user browser information for 3DS authentication, which will be sent to authentication service provider. - Usage Instruction 1. In Evonet, each merchant is configured with Non-Authentication, Optional-Authentication and Must-Authentication. When store is configured Optional-Authentication or Must-Authentication this object is applied. 2. Mandatory when the field authentication.type = threeDSIntegrator. - `acceptHeader` string, required — The accept header value of user browser - Usage Instruction 1. Field Type: String(2048) - `colorDepth` string, required — The color depth of the user browser, in pixels. - Usage Instruction 1. Use the screen.colorDepth property of the browser to get the value 2. Accepted value: 1, 4, 8, 15, 16, 24, 32, 48 bits 3. Field Type: String(2) - `javaEnabled` boolean, required — A boolean value indicating whether the user's browser is able to execute Java - `language` string, required — The value that represents the browser language defined in IETF BCP47, - Usage Instruction 1. returned from the navigator.language property. Examples: en-GB 2. Field Type: String(8). - `screenHeight` string, required — The total height of the user's screen in pixels. - Usage Instruction 1. The value is returned from the screen.height property. 2. Field Type: String(6). - `screenWidth` string, required — The total width of the user's screen in pixels. - Usage Instruction 1. The value is returned from the screen.width property. 2. Field Type: String(6). - `timeZoneOffset` string, required — The time difference between the UTC time and the local time of the user's browser, in minutes. - Usage Instruction 1. The value is got from the getTimezoneOffset() method. For example, "-120". 2. Field Type: String(5). - `userAgent` string, required — The user agent value of the user's browser. - Usage Instruction 1. Field Type: String(2048). - `userInfo` object — Detailed information about the buyer - Usage Instruction 1. Used in POST Payment request and POST PaymentMethod request, to send the buyer's information. 2. Specify this parameter if you can obtain the information from the user. This helps Evonet laundering and fraud detection, and increases payment success rates. - `nameEn` object — Buyer name in English - `familyName` string, required — The family name of user - `givenName` string, required — The given name of user - `nameLocal` object — Buyer name in local language 1. For POST Payment request, this field must be present when paymentMethod.type=bankTransfer and paymentBrand=Bank_Transfer_JPN. 2. For POST Payment request, when paymentMethod.type=bankTransfer and paymentBrand=PayEasy, decide whether this field needs to be submitted. You can call Get PaymentMethod API to query or consult your acquirer for confirmation. - `familyName` string, required — The given name of user - `givenName` string, required — The given name of user - `nameZh` object — Buyer name in Chinese 1. For POST Payment request, this field must be present when paymentMethod.type=bankTransfer and paymentBrand=Bank_Transfer_JPN. 2. For POST Payment, this field must be present when paymentMethod.type=buyNowPayLater and paymentBrand=Paidy. 3. For POST Payment request, when paymentMethod.type=bankTransfer and paymentBrand=PayEasy, decide whether this field needs to be submitted. You can call Get PaymentMethod API to query or consult your acquirer for confirmation. - `familyName` string, required — The given name of user - `givenName` string, required — The given name of user - `homePhone` object — The home phone number provided by user. - Usage Instruction: Refer to ITU-E.164 for additional information on format and length. - `countryCode` string — The country code sections of the homePhone. - `subscriberSections` string, required — The subscribe sections of the homePhone. - `mobilePhone` object — The mobile phone number provided by user. - Usage Instruction: 1. Refer to ITU-E.164 for additional information on format and length. 2. When authentication.type is FIDOPage, threeDSPageOrFIDOPage or threeDSIntegratorOrFIDOPage,this field is mandatory if no email address(userInfo.email) is provided. 3. For POST Payment, this field must be present when paymentMethod.type=bankTransfer and paymentBrand=Bank_Transfer_JPN. 4. For POST Payment request, when paymentMethod.type=bankTransfer and paymentBrand=PayEasy, decide whether this field needs to be submitted. You can call Get PaymentMethod API to query or consult your acquirer for confirmation. - `countryCode` string — The country code sections of the mobilePhone. - Usage Instruction: 1. When authentication.type is FIDOPage, threeDSPageOrFIDOPage or threeDSIntegratorOrFIDOPage,this field is mandatory. - `subscriberSections` string, required — The subscribe sections of the mobilePhone. - `workPhone` object — The work phone number provided by user. - Usage Instruction: Refer to ITU-E.164 for additional information on format and length. - `countryCode` string — The country code sections of the workPhone. - `subscriberSections` string, required — The subscribe sections of the workPhone. - `email` string, required — User's email address -Usage Instruction 1. For POST Payment, if paymentMethod.buyNowPayLater.paymentBrand=afterpay, this field must be present 2. When authentication.type is FIDOPage, threeDSPageOrFIDOPage or threeDSIntegratorOrFIDOPage,this field is mandatory if no no phone number(userInfo.mobilePhone) is provided. 3. If paymentMethod.onlineBanking.paymentBrand is DP_BDOInternetBanking、DP_MetrobankOnlineBanking、DP_LandbankATMOnline、DP_BPIOnline、DP_ChinabankOnlineBillsPayment、DP_RCBCOnlineBanking、DP_PNBInternetBankingBillsPayment、DP_SecurityBankCashPayment、DP_EastWestOnlinePayment、DP_AUBOnlinePayment、Dragonpay, this field is mandatory. - `reference` string — The User ID obtained or assigned by merchant, and used for merchant reference - Usage Instruction 1. This field is mandatory when Evonet needs to generate token, which is as the reference for the token. 2. For POST PaymentMethod, this field must be present 3. For POST Payment, if paymentMethod.type.card.tokenize=true, this field must be present 4. For PUT PaymentMethod request, this field is used to update token 5. Field Type: String(64) - `locale` string — Language in which the app communicates or merchant page with the customer. Based on ISO format for language (ISO 639-1) and alpha 2 country code (ISO 3166-1 alpha-2). The language and country should be separated using an underscore ( _ ). e.g. en_US. - `accountInfo` object — The user account information for 3D Secure 2, which will be sent to authentication service provider - Usage Instruction 1. This is optional in Evonet 2. If merchant wants to send this information, please refer to Authentication Appendix for detail field definition - `accountAgeIndicator` 'notApplicable' | 'thisTransaction' | 'lessThan30Days' | 'from30To60Days' | 'moreThan60Days' — Length of time that the cardholder has had the account with the Transaction Requestor. - `accountChangeDate` string — Date that the cardholder’s account with the Transaction Requestor was last changed, including Billing or Shipping address, new payment account, or new user(s) added. - Usage Instruction: 1. Format: YYYYMMDD 2. Field Type: String(8) - `accountChangeIndicator` 'thisTransaction' | 'lessThan30Days' | 'from30To60Days' | 'moreThan60Days' — Length of time since the cardholder’s account information with the Transaction Requestor was last changed, including Billing or Shipping address, new payment account, or new user(s) added. - `accountCreationDate` string — Date that the cardholder opened the account with the Transaction Requestor. - Usage Instruction: 1. Format: YYYYMMDD 2. Field Type: String(8) - `passwordChangeDate` string — Date that cardholder’s account with the Transaction Requestor had a password change or account reset. - Usage Instruction: 1. Format: YYYYMMDD 2. Field Type: String(8) - `passwordChangeDateIndicator` 'notApplicable' | 'thisTransaction' | 'lessThan30Days' | 'from30To60Days' | 'moreThan60Days' — Indicates the length of time since the cardholder’s account with the Transaction Requestor had a password change or account reset. - `purchasesLast6Months` string — Number of purchases with this cardholder account during the previous six months. - `addCardAttemptsDay` string — Number of Add Card attempts in the last 24 hours. - `pastTransactionsDay` string — Number of transactions (successful and abandoned) for this cardholder account with the Transaction Requestor across all payment accounts in the previous 24 hours. - Usage Instruction: 1. Sample: 2, 02, 002 2. Field Type: String(3) - `pastTransactionsYear` string — Number of transactions (successful and abandoned) for this cardholder account with the Transaction Requestor across all payment accounts in the previous year. - Usage Instruction: 1. Sample: 2, 02, 002 2. Field Type: String(3) - `paymentAccountAge` string — Date that the payment account was enrolled in the cardholder’s account with the Transaction Requestor. - Usage Instruction: 1. Format: YYYYMMDD 2. Field Type: String(8) - `paymentAccountIndicator` 'notApplicable' | 'thisTransaction' | 'lessThan30Days' | 'from30To60Days' | 'moreThan60Days' — Indicates the length of time that the payment account was enrolled in the cardholder’s account with the Transaction Requestor. - `deliveryAddressUsageDate` string — Date when the shipping address used for this transaction was first used with the Transaction Requestor. - Usage Instruction: 1. Format: YYYYMMDD 2. Field Type: String(8) - `deliveryAddressUsageIndicator` 'thisTransaction' | 'lessThan30Days' | 'from30To60Days' | 'moreThan60Days' — Indicates when the shipping address used for this transaction was first used with the Transaction Requestor. - `shippingNameIndicator` boolean — Indicates if the Cardholder Name on the account is identical to the shipping Name used for this transaction. - Value defined: true: Account Name identical to shipping Name false: Account Name different than shipping Name - Usage Instruction: 1. Field Type: Boolean - `suspiciousActivity` boolean — Indicates whether the Transaction Requestor has experienced suspicious activity (including previous fraud) on the cardholder account. - Value defined: true: Suspicious activity has been observed false: No suspicious activity has been observed - Usage Instruction: 1. Field Type: Boolean - `deliveryAddress` object — The delivery address. Mandatory if Authentication Service Provider uses it as the authentication way. - `city` string — City portion of the shipping address requested by the Cardholder. - `country` string, required — Country of the shipping address requested by the Cardholder. - Usage Instruction: 1. Defined in ISO-3166-1 alpha-3. For example, HKG. 2. Field Type: String(3) - `addressLine1` string — First line of the street address or equivalent local portion of the shipping address requested by the Cardholder. - Usage Instruction: 1. When authentication.type is FIDOPage, threeDSPageOrFIDOPage or threeDSIntegratorOrFIDOPage and userInfo.deliveryAddress is exist,this field is mandatory. - `addressLine2` string — The second line of the street address or equivalent local portion of the shipping address requested by the Cardholder. - `addressLine3` string — The third line of the street address or equivalent local portion of the shipping address requested by the Cardholder. - `postalCode` string, required — The ZIP or other postal code of the shipping address requested by the Cardholder. - `stateOrProvince` string — The state or province of the shipping address associated with the card being used for this purchase. - Value defined The accepted values of this field, please refer to ISO Alpha Country subdivision Code of the Appendix 8.9 State and Province Code - Usage Instruction: 1. Should be the country subdivision code defined in ISO 3166-2. 2. For example, using the ISO entry US-CA (California, United States), the correct value for this field = CA. Note that the country and hyphen are not included in this value. 3. Field Type: String(3) - `billingAddress` object — The billing address, which will be passed to authentication service provider - Usage Instruction 1. For POST Payment, this field must be present when paymentMethod.type=buyNowPayLater and paymentBrand=Paidy. - `city` string — City portion of the shipping address requested by the Cardholder. - `country` string, required — Country of the shipping address requested by the Cardholder. - Usage Instruction: 1. Defined in ISO-3166-1 alpha-3. For example, HKG. 2. Field Type: String(3) - `addressLine1` string — First line of the street address or equivalent local portion of the Cardholder billing address associated with the card used for this purchase. - Usage Instruction: 1. When authentication.type is FIDOPage, threeDSPageOrFIDOPage or threeDSIntegratorOrFIDOPage and userInfo.billingAddress is exist,this field is mandatory. 2. For POST Payment, this field must be present when paymentMethod.type=buyNowPayLater and paymentBrand=Paidy. - `addressLine2` string — Second line of the street address or equivalent local portion of the Cardholder billing address associated with the card used for this purchase. - Usage Instruction: 1. For POST Payment, this field must be present when paymentMethod.type=buyNowPayLater and paymentBrand=Paidy. - `addressLine3` string — The third line of the street address or equivalent local portion of the shipping address requested by the Cardholder. - `postalCode` string, required — The ZIP or other postal code of the shipping address requested by the Cardholder. - `stateOrProvince` string — The state or province of the shipping address associated with the card being used for this purchase. - Value defined The accepted values of this field, please refer to ISO Alpha Country subdivision Code of the Appendix 8.9 State and Province Code - Usage Instruction: 1. Should be the country subdivision code defined in ISO 3166-2. 2. For example, using the ISO entry US-CA (California, United States), the correct value for this field = CA. Note that the country and hyphen are not included in this value. 3. For POST Payment, this field must be present when paymentMethod.type=buyNowPayLater and paymentBrand=Paidy. 3. Field Type: String(3) - `subMerchantInfo` object, required - `merchantID` string — Merchant ID - Usage Instruction 1. Field Type: String(64) - `descriptor` string — The Dynamic Billing Descriptor - `webhook` string — This filed is used for merchant to provide asynchronous notification endpoint - Usage Instruction 1. Merchant may provide this information in the request message, once it is processed successfully, Evonet will send notification to this endpoint 2. The format of the webhook must contain http:// or htps:// 3. Field Type: String(300) - `metadata` string — This field is used for merchant to state reference information - Usage Instruction 1. If merchant sends this field in the request message, Evonet will echo it back in the response 2. Field Type: String(512) ## Response `200` - object - `result` object, required — The result information for the transaction processed - Usage Instruction 1. Used in the response of PaymentMethod, Payment, Capture, Cancel and Refund - `code` string, required — This is the code of result from Evonet about the transaction processed - Value defined Refer to . - Usage Instruction 1. Field Type: String(8) - `message` string, required — This is the description about the code of result - Value defined Refer to . - Usage Instruction 1. Field Type: String(1024) - `category` 'M' | 'N' | 'E' | 'S' | 'H' | 'R' — The category of the response code. - `pspResponseCode` string — This is the Response code from the PSP. - Usage Instruction 1. If the PSP returns a response code for the transaction, Evonet will forward to merchant in this field 2. Field Type: String(1024) - `pspMessage` string — This is the Response code from the PSP. - Usage Instruction 1. If the PSP returns a response code for the transaction, Evonet will forward to merchant in this field 2. Field Type: String(1024) - `action` object — This object is to define the next step action for merchant or Evonet, with the related data when performing the action - `type` 'threeDSRedirect' | 'threeDSIdentify' | 'threeDSChallenge' | 'inputMobilePhone' | 'inputOTP' | 'redirectUser' | 'redirectInIframe' | 'presentQRCode' | 'invokeWallet' | 'resendOTP' | 'presentEcontext' | 'promptUser' | 'completed', required — This field includes the action type for merchant or Evonet to perform: The description of each value, please refer to Appendix 8.9 Action Type - Usage Instruction Field Type: String(32) - `threeDSData` object — This object is the data when performing the action when action.type=threeDSRedirect, threeDSIdentify or threeDSChallenge. - `url` string — The URL address. Merchant redirects the user to this URL by the method specified in action.threeDSData.method. -Usage Instruction 1. When performing 3DS authentication in threeDSPage mode, this field in the POST PaymentMethod or POST Payment response message, with action.type=threeDSRedirect, specifies the Evonet hosted authentication page, which is a blank page that completes the complex authentication process with different card schemes. 2. When performing 3DS authentication in threeDSIntegrator mode, this field in the POST PaymentMethod or POST Payment response message, with action.type=threeDSRedirect, threeDSIdentify or threeDSChallenge, specifies the card scheme or issuer authentication page. Field Type: String(2048) - `method` 'GET' | 'POST' — The HTTP method when performing the redirection. - Usage Type Field Type: String(8) - `parameter` object — The 3DS redirection parameter returned by Evonet. Merchant needs to submit the parameter(s) in this object when redirect to action.threeDSData.url. - `PaReq` string — The 3DS request data for the issuer. -Usage Instruction When performing 3DS authentication in threeDSIntegrator mode, this field in the POST PaymentMethod or POST Payment response message, with action.type=threeDSRedirect, specifies the required data that merchant needs to POST as a form element to the 3DS authentication page. Field Type: String(30000) - `MD` string — The payment session identifier returned by the card issuer. -Usage Instruction When performing 3DS authentication in threeDSIntegrator mode, this field in the POST PaymentMethod or POST Payment response message, with action.type=threeDSRedirect, specifies the required data that merchant needs to POST as a form element to the 3DS authentication page. Field Type: String(300) - `TermUrl` string — After completing 3DS authentication on the card issuer site, the user is redirected back to the merchant site. This URL value specifies which merchant site page the user goes back to. -Usage Instruction When performing 3DS authentication in threeDSIntegrator mode, this field in the POST PaymentMethod or POST Payment response message, with action.type=threeDSRedirect, specifies the required data that merchant needs to POST as a form element to the 3DS authentication page. Field Type: String(300) - `creq` string — The 3DS Challenge request data for the issuer. -Usage Instruction When performing 3DS authentication in threeDSIntegrator mode, this field in the PUT PaymentMethod or PUT Payment response message, with action.type=threeDSChallenge, specifies the required data that merchant needs to POST as a form element to the 3DS authentication page. Field Type: String(30000) - `threeDSMethodData` string — The 3DS Method Data. The base64 data need the user's bowser sends to ACS URL(action.threeDS.url). -Usage Instruction When performing 3DS authentication in threeDSIntegrator mode, this field in the POST PaymentMethod or POST Payment response message, with action.type=threeDSIdentify, specifies the required data that merchant needs to POST as a form element to the ACS URL. Field Type: String(2048) - `redirectData` object — This object is the data when performing the action when action.type = redirectUser or redirectInIframe. - `url` string, required — The URL to redirect to. Merchant redirects the user to this URL by the method specified in action.redirectData.method. -Usage Instruction 1. When performing the tokenization with Alipay, this field in the POST PaymentMethod response message, with action.type=redirectUser, specifies the Alipay pre-contract page for user to sign the agreement with Alipay. 2. When performing the payment with E-Wallets including (a) Alipay, Alipay+ and Jkopay on PC WEB, (b) Alipay, Alipay+, Alipay HK, WeChat Pay and Jkopay on Mobile WAP, and (c) WeChat Pay in Official Account, this field in the POST Payment response message, with action.type=redirectUser, specifies the wallet payment page for user to complete the payment. Same as when performing the payment with SecurePay for UnionPay on PC WEB, Mobile WAP and wallet APP. 3. When performing the payment with E-Wallet on PC WEB using Alipay HK, this field in the POST Payment response message, with action.type=redirectInIframe, specifies the wallet QR code page for user to scan and pay. Please note that instead of a simple redirection for the whole page, merchant need to render an iframe on its payment page and perform the redirection in the iframe to show the wallet QR code to guide user to pay. Note: If your Alipay merchant account is Alipay HK account, when performing the payment with E-Wallet on PC WEB using Alipay, also need redirect in the iframe. Field Type: String(4096) - `method` 'GET' | 'POST' — The HTTP method when performing the redirection. - Usage Instruction Field Type: String(8) - `parameter` string — The redirection parameter returned by Evonet. -Usage Instruction 1. When method = POST, merchant needs to send this field to redirectData.url with the HTTP POST. Field Type: String(4096) - `walletData` object — This object is the data when performing the action with action.type=invokeWallet. - `paymentString` string, required — The parameters required to invoke the wallet APP. Merchant invokes the wallet APP by a redirection with this parameter. -Usage Instruction 1. When performing the tokenization with WeChat Pay in WeChat Mini-Program, this field in the POST PaymentMethod response message, with action.type=invokeWallet, specifies the parameters required to invoke WeChat Pay pre-contract page for user to sign the agreement with WeChat Pay. 2. When performing the payment with WeChat Mini-Program or Alipay, Alipay HK or WeChat Pay in their wallet APP, this field in the POST Payment response message, with action.type=invokeWallet, specifies the parameters required to invoke the wallet APP payment page for user to complete the payment. Field Type: String(20000) - `paymentMethod` object — This field includes the Payment Method information, including Payment Method selected by User for Payment, and the Payment Method supported by the merchant - Usage Instruction 1. For GET PaymentMethod response, If merchant sends merchantTransID in GET PaymentMethod request, Evonet will return this object. 2. Evonet may include this object in response. - `status` 'verify_pending' | 'tokenized_pending' | 'tokenized' | 'verify_declined' | 'tokenized_declined', required — The status of Original PaymentMethod transaction - Usage Instruction 1. Field Type: String(20) - `failureCode` string — Error code returned for the PaymentMethod. - Value defined Refer to . - Usage Instruction 1. Only returned when the paymentMethod.status=Failed 2. Field Type: String(8) - `failureReason` string — Error message returned for the PaymentMethod. - Value defined Refer to . - Usage Instruction 1. Only returned when the paymentMethod.status=Failed 2. Field Type: String(1024) - `merchantTransInfo` object, required — This is the information of merchantTransInfo from the request of the initial PaymentMethod transaction - `merchantTransID` string, required — This is the merchantTransID from the initial PaymentMethod transaction - Usage Instruction 1. Field Type: String(32) - `merchantOrderReference` string — This is the merchantOrderReference from the initial PaymentMethod transaction - Usage Instruction 1. Field Type: String(32) - `merchantTransTime` string, date-time, required — This is the merchantTransTime from the initial PaymentMethod transaction - Usage Instruction 1. Format: ISO 8601 YYYY-MM-DDThh:mm:ssTZD 2. Sample: 2017-07-17T13:42:40+01:00 - `card` object — This field is to send card related information for this transaction -Usage Instruction: 1. For POST Payment or POST PaymentMethod. If paymentMethod.type = card, the field must be present 2. For PUT PaymentMethod. Merchant may send this field to update the card information corresponding to the token and the profile of the token. 3. Evonet may include this object in response 4. For POST Payment or POST PaymentMethod response. If paymentMethod.type=GooglePay & The paymentMethod.encryptedData is a card that consists of PAN, the field will be present. - `first6No` string, required — The first 6 digits of the card number - Usage Instruction 1. This field is used in response from Evonet 2.For POST Payment or POST PaymentMethod response. If paymentMethod.type=GooglePay & The paymentMethod.encryptedData is a card that consists of PAN, the field will be present. 3. Field Type: String(6) - `last4No` string, required — The last 4 digits of the card number - Usage Instruction 1. This field is used in response from Evonet 2.For POST Payment or POST PaymentMethod response. If paymentMethod.type=GooglePay & The paymentMethod.encryptedData is a card that consists of PAN, the field will be present. 3. Field Type: String(4) - `paymentBrand` string — This is used to indicate the card scheme which the card belongs to - Value defined The accepted values of this field, please refer to card paymentMethod type of the Appendix 8.8 payment brands - Usage Instruction: 1. This is used in response from Evonet 2.For POST Payment or POST PaymentMethod response. If paymentMethod.type=GooglePay & The paymentMethod.encryptedData is a card that consists of PAN, the field will be present. 3. Field Type: String(32) - `fundingType` 'credit' | 'debit' | 'prepaid' — This is used to indicate the type of the card - Usage Instruction 1. This field is used in response from Evonet 2. Field Type: String(32) - `holderName` string — The cardholder name - Usage Instruction 1. This field is used in the response from Evonet 2. Field Type: String(50) - `issuingBank` string — The name of Issuing Bank - Usage Instruction 1. This field is used in response from Evonet 2. Field Type: String(16) - `issuingCountry` string — The card issuing country. - Usage Instruction 1. This field is used in response from Evonet 2. The three-character country code as defined in ISO-3166-1 alpha-3. For example, SGP. 3. Field Type: String(3) - `issuerCountry` string — The cardholder's country. - Usage Instruction 1. This field is used in response from Evonet 2. The three-character country code as defined in ISO-3166-1 alpha-3. For example, SGP. 3. Field Type: String(3) - `isCommercial` boolean — This is used to response whether the card is a business card. -Value defined true: this card is a business card false: this card is not a business card - Usage Instruction 1. This field is used in response from Evonet 2. Field Type: Boolean - `token` object — This is used to send token related Information for this transaction - Usage Instruction 1. For POST payment or PaymentMethod request, if paymentMethod.type = token, the field must be sent 2. For POST Payment or POST PaymentMethod response. If paymentMethod.type=GooglePay & The paymentMethod.encryptedData is a tokenized card that consist of device PAN and cryptograms, the field will be present. 3. Evonet may include this field in response - `value` string, required — The token value. - Usage Instruction 1. For POST Payment request, this must be sent when paymentMethod.type = token 2. For POST Payment response, this is used in response from Evonet 3. For PUT PaymentMethod and PUT Payment, this is used in response from Evonet 4.For POST Payment or POST PaymentMethod response. If paymentMethod.type=GooglePay & The paymentMethod.encryptedData is a tokenized card that consist of device PAN and cryptograms, the field will be set as masked device PAN. 5.For POST Payment or POST PaymentMethod response. If paymentMethod.type=GooglePay & paymentMethod.GooglePay.tokenize=true&The paymentMethod.encryptedData is a tokenized card that consist of device PAN and cryptograms, the field will be set as getewayToken value. 6. Field Type: String(64) - `expiryDate` string, date-time — This is the token expiration date and time -Usage Instruction 1. Evonet may include this field in response 2. If the token permanent valid, this filed will be not return. 3. Format: ISO 8601 YYYY-MM-DDThh:mm:ssTZD 4. Sample: 2017-07-17T13:42:40+01:00. 5. Field Type: Datetime - `userReference` string — The User ID obtained or assigned by merchant, and used for merchant reference - Usage Instruction 1. Evonet may include this field in response 2. The value of this field is same as userInfo.reference in your POST request. 3. Field Type: String(64) - `vaultID` string — The group ID which the token belongs to. This token is unique under same vault ID - Usage Instruction: 1. This ID is assigned in Evonet, and will be provided to customer before integration. 2. Evonet may include this field in response 3. Field Type: String(36) - `fingerprint` string — The token's fingerprint. - Usage Instruction 1. Evonet may include this field in response 2. Field Type: String(64) - `createTime` string, date-time — The token's created Datetime. -Usage Instruction 1. Format: ISO 8601 YYYY-MM-DDThh:mm:ssTZD 2. Sample: 2017-07-17T13:42:40+01:00. 3. Evonet may include this field in response 4. Field Type: Datetime - `updateTime` string, date-time — The token's last updated Datetime. -Usage Instruction 1. Format: ISO 8601 YYYY-MM-DDThh:mm:ssTZD 2. Sample: 2017-07-17T13:42:40+01:00. 3. Evonet may include this field in response 4. Field Type: Datetime - `status` 'disabled' | 'enabled' | 'expired', required — The status of token - Usage Instruction 1. Evonet may include this field in response 2. Field Type: String(20) - `first6No` string — The first 6 digits of the tokenized cards that consist of device PAN. - Usage Instruction 1. For POST Payment or POST PaymentMethod response. If paymentMethod.type = Google Pay&paymentMethod.GooglePay.tokenize=true&The paymentMethod.encryptedData is a tokenized card that consist of device PAN and cryptograms, the field will be present. 2. Field Type: String(6). - `last4No` string — The last 4 digits of the tokenized cards consist of device PAN. - Usage Instruction 1. For POST Payment or POST PaymentMethod response. If paymentMethod.type = Google Pay&paymentMethod.GooglePay.tokenize=true&The paymentMethod.encryptedData is a tokenized card that consist of device PAN and cryptograms, the field will be present. 2. Field Type: String(4). - `networkToken` object — This object is used to send network token related Information for this transaction - Usage Instruction 1. For POST PaymentMethod response, if the request generated a network token, the field will be present. - `status` 'enabled' | 'suspended' | 'disable', required — The status of Network Token - Usage Instruction 1. Field Type: String(32) - `supportDeviceBinding` boolean, required — Does current network token support device binding? - Value definition true: support false: unsupport -Uasge Instruction If current network token support device binding, you can use PUT PaymentMethod to continue the binding. - `tokenID` string, required — The unique ID of the network token assigned by card scheme - Usage Instruction 1. Evonet may include this field in response. 2. Field Type: String(64) - `first6No` string, required — The first 6 digits of the network token - Usage Instruction 1. This field is used in response from Evonet 2. Field Type: String(6) - `last4No` string, required — The last 4 digits of the network token - Usage Instruction 1. This field is used in response from Evonet 2. Field Type: String(4) - `expiryDate` string, required — The expiration date of the network token -Usage Instruction 1. Format: MMYY - `paymentAccountReference` string — Payment Account Reference (PAR) if available for this payment instrument. - Usage Instruction 1. This field is used in response from Evonet 2. Field Type: String(64) - `tokenReferenceID` string — It is a unique ID associated with a single token. - Usage Instruction 1. This field is used in response from Evonet 2. Field Type: String(64) - `recurringReference` string — The recurringReference that uniquely identifies the recurring transaction. Merchant will needs this to make future payments for the user. - Usage Instruction 1. For POST Payment response, PUT Payment response GET Payment response, Payment Notification , POST PaymentMethod response, PUT PaymentMethod response, GET PaymentMethod response and PaymentMethod Notification, it is generated by Evonet. 2. For POST Payment request, it is present for future payments. 3. Field Type: String(64) - `accountUpdateIndicator` 'Y' | 'N' — Account Update Indicator - Usage Instruction 1. This field is suitable for the paymentBrand=Visa - `authentication` object — The information used for User authentication with Card - Usage Instruction 1. Evonet supports securePlus and threeDS authentication types - `type` 'threeDSPage' | 'threeDSIntegrator' | 'FIDOPage' | 'threeDSPageOrFIDOPage' | 'threeDSIntegratorOrFIDOPage' — This is used for Evonet to response merchant which authentication type is applied for this transaction. - Usage Instruction: 1. In the request from merchant, only threeDSPage and threeDSIntegrator are applied 2. In the response from Evonet, all the values are applied. 3. If merchant is configured to support 3DS authentication in Evonet, merchant can send this field in the request of POST PaymentMethod and POST Payment, if not present, default value of threeDSPage is applied 4. If merchant is configured to support 3DS or SecurePlus authentication in Evonet, and authentication is performed, in the response of POST PaymentMerthod and POST Payment, Evonet will include this field to indicate the authentication type 5. In PUT Payment and PUT PaymentMethod request, the value this field must same as POST request, if not present, default value is threeDSPage. 6. Field Type: String(20) - `threeDS` object — This field includes the related information for 3DS authentication - Usage Instruction 1. Merchant can use this object to send information to Evonet for 3DS authentication 2. If authenticationOnly=true, Evonet sends the 3DS result data (mpiData) to merchant in this field. 3. Merchant can use this object to send 3DS result data (mpiData) to Evonet for payment. 4. If the authentication is finished, Evonet will return the eci and status in this object. 5. If the transaction has been verified by 3DS, Evonet sends the 3DS result data (mpiData) to merchant in this field. - `mpiData` object — The 3DS authentication result data - Usage Instruction 1. Evonet will response this data to merchant in POST Payment or PUT Payment response, if authenticationOnly=true in the request of POST Payment 2. Mandatory when merchant obtains this data from other service provider, and send to Evonet in POST Payment 3. Evonet will response this data to merchant in POST Payment, PUT Payment or GET Payment response, if the transaction has been verified by 3DS. - `status` 'Y' | 'N' | 'U' | 'A' | 'C' | 'R' — The raw result of the 3DS to indicate the status of the E-Commerce transaction, used for the follow-up authorization request. - Usage Instruction 1. Field Type: String(1). - `transStatusReason` string — 3DS result reason - Usage Instruction 1. The description of each value, please find in appendix 8.10 2. Field Type: String(2). - `cardholderInfo` string — Text provided by the ACS/Issuer to Cardholder during a Frictionless transaction that was not authenticated by the ACS. The Issuer can optionally provide information to Cardholder. - Usage Instruction 1. Field Type: String(1024). - `cavv` string — The cavv. The field is authentication value(AV) for 3DS 2.0. The base64 encoded value is accepted or returned in this field. - Usage Instruction 1. Field Type: String(28). - `eci` string — The electronic commerce indicator. - Usage Instruction 1. Field Type: String(2). - `dsTransID` string — dsTransID - Usage Instruction 1. Mandatory for 3D Secure 2 2. Field Type: String (36) - `threeDSVersion` string — threeDSVersion - Usage Instruction 1. Mandatory for 3D Secure 2. 2. The current version supported is 2.1.0. 3. Field Type: String(10). - `isFrictionless` 'Y' | 'N' — This field is used to indicate the mode of the 3DS is frictionless or challenge - `metadata` string — This field is used for merchant to state reference information - Usage Instruction 1. If merchant sends this field in the request message, Evonet will echo it back in the response 2. Field Type: String(512) --- [API](https://skmtc.net/evonetonline/apis/evonet-api.md) · [All operations](https://skmtc.net/evonetonline/apis/evonet-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/evonetonline/evonet-api/versions/2136e26ceb19/schema)