Merchant Transaction Approval Rate Optimization Best Practices
This document provides Evonet payment platform merchants with a systematic guide to core optimization strategies that effectively improve transaction authorization approval rates. By enabling digital wallets, configuring Address Verification Service (AVS), and enriching EMV 3DS transaction payloads, merchants can significantly reduce issuer risk false-positive rates and chargeback ratios while maximizing payment conversion—all within full compliance.
🌐 Language Switch / 语言切换
1. Enable Digital Wallets (Apple Pay & Google Pay)
Compared to standard manual card entry, integrating digital wallets can significantly increase issuer trust and authorization conversion rates.
Performance Impact: Portfolio data shows that digital wallets play a highly significant role in boosting approval rates in Western markets. The conversion advantage is especially prominent for cardholder traffic in the European (EU) and United States (USA) regions.
Supported Card Schemes: Wallet integration currently supports only Visa and Mastercard. JCB and other card schemes are not yet supported.
Integration Methods:
| Merchant Type | Integration Details |
|---|---|
| LinkPay Merchants | Natively built into the checkout products and deeply optimized. No additional development is required. |
| Drop-in Merchants | Some configuration is reuqired, but no development is needed. Please refer to: https://developer.evonetonline.com/docs/apple-pay https://developer.evonetonline.com/docs/google-pay |
| Direct API Merchants | If you are integrating via the Direct API, you need to complete the relevant development and integration with the GP/AP. please refer to: https://developer.evonetonline.com/v1.0/docs/apple-pay https://developer.evonetonline.com/v1.0/docs/google-pay |
2. Address Verification Service (AVS)
AVS compares the billing address entered by the cardholder with the information on file at the issuing bank to reduce fraud risk in card-not-present transactions and boost authorization confidence.
Core Markets: AVS is a crucial conversion booster in specific markets, with the most significant effects observed on traffic from the United Kingdom, Canada, and the United States.
How to Enable AVS via API
If you need to enable the AVS fraud prevention check, please complete the following configuration adjustments in your integration (we recommend verifying in the test/sandbox environment first):
- Add and set the field
"allowAvsCheck": truein the outermost layer of the request payload. - Accurately submit the cardholder's billing address by integrating the following complete fields:
userInfo.billingAddress.addressLine1userInfo.billingAddress.postalCodeuserInfo.billingAddress.cityuserInfo.billingAddress.country
- Ensure that the submitted address text format complies with standard specifications, avoiding special characters or misplacements.
- The following AVS response-related fields will be added to the transaction Response and Webhook:
payment.pspTransInfo.avsCheckResultRawpayment.pspTransInfo.avsCheckResult
The validation results within these fields are uniformly parsed and processed by internal logic.
- The transaction details page in the Merchant Platform will automatically activate and display a brand new AVS information module.
For details, please refer to: AVS（Address Verification Service）Function Description
3. EMV 3DS Minimum Data Requirements and Best Practices
High-quality transaction payloads can significantly reduce the false-positive rate of issuing banks' risk management, maximize the 3DS frictionless authentication flow, and lower the chargeback rate.
3.1 Minimum Mandatory Field Requirements (All Integrations)
According to the global compliance requirements of Visa and Mastercard, the following fields are the minimum mandatory items in standard 3DS transaction payloads for major regions (United States, Canada, Europe, APAC, Latin America). Submitting null values, fixed static fake values, or false test data is strictly prohibited.
| Data Category | Eligible Compliance Fields (Submit at least one per category) | Direct API Merchants | LinkPay / Drop-in Checkout Merchants |
|---|---|---|---|
| Cardholder Identifier | · Email Address · Phone Number (Work/Home/Mobile) · Full Name | Encapsulated and submitted within the userInfo object | Encapsulated and submitted within the userInfo object |
| Address / Delivery | · Billing Address Line 1 + postalCode + country · Shipping Address Line 1 + postalCode + country | Encapsulated and submitted within the userInfo object | Encapsulated and submitted within the userInfo object |
| Technical | · Browser or Device IP Address · Device ID · Device Latitude/Longitude / SDK APP ID | Encapsulated and submitted within the transInitiator object | No merchant action required. Automatically collected and 100% populated by the server |
3.2 Recommended Best Practices (Direct API Only)
In addition to meeting the minimum mandatory requirements, Direct API merchants are recommended to further supplement the payload with the following additional environment data. Providing this data helps issuing banks make more accurate decisions, thereby maximizing the payment approval rate.
Identity Data Elements
| Recommended Fields | Evonet API Field Mapping |
|---|---|
| Cardholder Billing Address | userInfo.billingAddress (including postalCode, addressLine1, city, country) |
| Full Shipping Address | userInfo.deliveryAddress (all detailed sub-fields) |
Account Information
| Recommended Fields | Evonet API Field Mapping |
|---|---|
| Account Age / Change Indicator | userInfo.accountInfo.accountAgeIndicator |
| Account Creation Date | userInfo.accountInfo.accountCreationDate |
| Suspicious Account Activity | userInfo.accountInfo.suspiciousActivity |
Browser / Device Information
| Recommended Fields | Evonet API Field Mapping |
|---|---|
| Accept Header | transInitiator.acceptHeader |
| User Agent | browserInfo.userAgent |
| Java Enabled | browserInfo.javaEnabled |
| Language | browserInfo.language |
| Color Depth | browserInfo.colorDepth |
| Screen Height | browserInfo.screenHeight |
| Screen Width | browserInfo.screenWidth |
| Time Zone | browserInfo.timeZoneOffset |
Note: The above best-practice fields are not mandatory, but supplementing them can effectively enhance the accuracy of issuing banks' authorization decisions. Merchants are advised to integrate them selectively based on business scenarios.
For detailed field information, please refer to: POST /payment
一、启用数字钱包（苹果支付 & 谷歌支付）
与标准的手输卡号相比，集成数字钱包能够大幅提升发卡行的信任度及授权转化率。
性能表现：大盘数据显示，数字钱包在欧美市场具有极为显著的成功率提升作用。对于欧洲（EU）和美国（USA）地区的持卡人流量，其转化优势尤为突出。
支持卡组：目前钱包集成仅支持 Visa 和 Mastercard，暂不支持 JCB 等其他卡组。
接入方式：
| 商户类型 | 接入说明 |
|---|---|
| LinkPay 商户 | 已在收银台产品中原生内置并完成深度优化，商户无需额外开发。 |
| Drop-in 商户 | 需要完成一些配置，无需开发。请参考：https://developer.evonetonline.com/docs/apple-pay https://developer.evonetonline.com/docs/google-pay |
| Direct API 商户 | 如您使用直连 API 接入，需与 GP/AP 完成相关开发对接。请参考：https://developer.evonetonline.com/v1.0/docs/apple-pay https://developer.evonetonline.com/v1.0/docs/google-pay |
二、地址验证服务（AVS）
AVS 通过比对持卡人输入的账单地址与发卡行系统留存信息，降低非面对面交易的欺诈风险，并增强授权信心。
核心市场：AVS 是特定市场极其重要的转化助推器，对于来自英国、加拿大和美国的流量效果最为显著。
如何通过 API 开启 AVS
商户如需启用 AVS，请在集成中完成以下配置调整（建议先在沙箱环境验证）：
- 在请求报文的最外层结构中，添加并设置字段
"allowAvsCheck": true。 - 准确上送持卡人账单地址信息，对应接入以下全量字段：
userInfo.billingAddress.addressLine1userInfo.billingAddress.postalCodeuserInfo.billingAddress.cityuserInfo.billingAddress.country
- 确保上送的地址文本格式符合标准规范，避免特殊符号或错位。
- 交易响应和异步通知中将新增 AVS 应答字段：
payment.pspTransInfo.avsCheckResultRawpayment.pspTransInfo.avsCheckResult
校验结果由内部逻辑统一解析处理。
- 商户后台交易详情页面将自动激活并展示全新的 AVS 信息模块。
具体请参考：AVS（Address Verification Service）功能说明
三、EMV 3DS 最低数据要求与最佳实践
高质量的交易报文能大幅降低发卡行风控的误判率，最大化 3DS 免密无摩擦流程（Frictionless），并有效降低拒付率。
3.1 最低必填字段要求（所有集成方式通用）
根据 Visa 与 Mastercard 的全球合规要求，以下字段为主要地区（美国、加拿大、欧洲、亚太、拉丁美洲）标准 3DS 交易报文中的最低强制必填项。严禁上送空值（Null）、固定静态假值或虚假测试数据。
| 数据大类 | 可选合规字段（每类至少上送一个） | Direct API 商户 | LinkPay / Drop-in 收银台商户 |
|---|---|---|---|
| 持卡人身份识别 | · 电子邮箱地址 · 电话号码（工作/家庭/手机） · 持卡人姓名 | 封装在 userInfo 对象体内上送 | 封装在 userInfo 对象体内上送 |
| 地址与物流信息 | · 账单地址第一行 + postalCode + country · 收货地址第一行 + postalCode + country | 封装在 userInfo 对象体内上送 | 封装在 userInfo 对象体内上送 |
| 技术与环境参数 | · 浏览器或设备 IP 地址 · 设备 ID · 设备经纬度 / SDK APP ID | 封装在 transInitiator 对象体内上送 | 无需商户处理，由服务器端自动采集并 100% 补全 |
3.2 最佳实践推荐（仅 Direct API 商户）
除满足最低必填要求外，建议 Direct API 商户在报文中进一步补充以下额外环境数据。提供这些数据能帮助发卡行做出更准确的决策，从而最大化支付通过率。
身份数据元素
| 推荐提供字段 | Evonet API 字段映射 |
|---|---|
| 持卡人账单地址 | userInfo.billingAddress（含 postalCode、addressLine1、city、country） |
| 完整收货地址 | userInfo.deliveryAddress（全量细分字段） |
持卡人账户信息
| 推荐提供字段 | Evonet API 字段映射 |
|---|---|
| 账户创建/修改时长指示符 | userInfo.accountInfo.accountAgeIndicator |
| 账户创建日期 | userInfo.accountInfo.accountCreationDate |
| 可疑账户活动 | userInfo.accountInfo.suspiciousActivity |
设备环境参数
| 推荐提供字段 | Evonet API 字段映射 |
|---|---|
| 接受标头（Accept Header） | transInitiator.acceptHeader |
| 用户代理（User Agent） | browserInfo.userAgent |
| 是否启用 Java | browserInfo.javaEnabled |
| 语言（Language） | browserInfo.language |
| 色彩深度（Color Depth） | browserInfo.colorDepth |
| 屏幕高度（Screen Height） | browserInfo.screenHeight |
| 屏幕宽度（Screen Width） | browserInfo.screenWidth |
| 时区（Time Zone） | browserInfo.timeZoneOffset |
注意：以上最佳实践字段并非强制要求，但补充完整后可有效提升发卡行授权决策的精准度，建议根据业务场景择优接入。
详细字段信息请参考：POST /payment