...

❔ Expected Outcome

VISA Data Requirements

1. The remaining fields of the 12 originally communicated as being required in AI13277 will be reverted to “required conditional” with the next publication of the Visa Secure Program Guide.

2. At least one phone number out of work, home or mobile must be provided.

3. It is recommended to provide both phone and email data fields for authentication; however, if the market only collects one of the data fields, then providing one of the two options satisfies the minimum data requirement.

4. Only for browser-based transactions

5. Except in markets where the billing address fields do not exist

6. Only for SDK transactions

Must-Haves

1. Accurate Data Collection and Transmission of all Mandatory fields

   • Description: Ensure the collection of the mandatory customer data for Visa transactions

   • Rationale: This is critical to comply with Visa's requirements, preventing transaction rejections and avoiding potential legal and regulatory issues.

   • Perceived Business Value: High. Compliance with Visa's requirements will ensure uninterrupted transaction processing, maintain customer trust, and avoid legal penalties.

2. Integration with SIBS PAYCOMET for Accurate Data Transmission

   • Description: Modify the integration with SIBS PAYCOMET to transmit the newly required accurate customer data instead of fake values.

   • Rationale: Directly addresses the core issue of sending fake data, ensuring that Visa transactions are processed correctly.

   • Perceived Business Value: High. Ensures compliance, reduces risk of transaction rejections, and upholds the platform's reliability.

3. Integration with PAYCOMET SIBS for Accurate Data Transmission

   • Description: Modify the integration with PAYCOMET SIBS to transmit the newly required accurate customer data instead of fake values.

   • Rationale: Directly addresses the core issue of sending fake data, ensuring that Visa transactions are processed correctly.

   • Perceived Business Value: High. Ensures compliance, reduces risk of transaction rejections, and upholds the platform's reliability.

...

1. Accurate Data Collection and Transmission of all Recommended fields

   • Description: Ensure the collection of the mandatory customer data for Visa transactions

   • Rationale: This is critical to comply with Visa's requirements, preventing transaction rejections and avoiding potential legal and regulatory issues.

   • Perceived Business Value: High. Compliance with Visa's requirements will ensure uninterrupted transaction processing, maintain customer trust, and avoid legal penalties.

❓ Open questions

1. Which fields will be mandatory or optional?

2. To mandatory fields will we add the asterisk in front of the field label/placeholder?

3. Currently, the mandatory validation messages are displayed one by one as the user is filling in. Are we going to follow this behavior? My suggestion is to change this behavior and display all the mandatory messages at the same time. We should change this for the older fields as well.

4. The email and phone number will be pre-filled. In the case of the phone number, will we get this info from the user data or the phone number provided on the delivery details section on the cart page?

5. In case the user enters a credit card of the Mastercard type, will we continue to require the fields, display the fields, and send this information to Paycoment?

6. If the user chooses the "Ticket Restaurant” what will be going on?

7. How will we deal with the vaulted cards?

📈 Success Metrics

...