You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am writing to bring attention to a critical issue regarding the validation of fields during the initialization of the payment form in the Iyzipay payment service. As a prominent payment service, it is crucial to ensure robust validation mechanisms to enhance user experience and facilitate seamless integration.
Problem:
The issue lies in the lack of clear and informative validation messages for the various fields accepted. Specifically, the validation for certain fields is not transparent, leading to confusion and frustration during integration.
Example:
Consider a scenario where a software system sets its testing environment with user emails in the format [email protected]. If the sandbox of Iyzipay cannot accept this format, the service needs to raise a validation error related to this specific field. However, in the current version, the service returns an error message stating "invalid signature," which is unclear and does not provide sufficient information about the root cause of the issue.
Request:
I request that the validation mechanism for the initialization of the payment form be revisited and improved to provide more explicit and user-friendly error messages. This enhancement will greatly benefit developers integrating with Iyzipay by reducing the time spent diagnosing issues and ensuring a smoother overall experience.
Expected Outcome:
Clear and specific validation messages for each field, highlighting the nature of the error.
Informative responses that guide developers in resolving issues efficiently.
Improved documentation regarding field-specific validation requirements.
Steps to Reproduce:
Use a testing environment with user emails in the format [email protected].
Attempt to initialize the payment form.
Observe the error message received, which currently states "invalid signature."
Thank you for your attention to this matter, and I appreciate your efforts in continuously improving the Iyzipay payment service.
The text was updated successfully, but these errors were encountered:
I am writing to bring attention to a critical issue regarding the validation of fields during the initialization of the payment form in the Iyzipay payment service. As a prominent payment service, it is crucial to ensure robust validation mechanisms to enhance user experience and facilitate seamless integration.
Problem:
The issue lies in the lack of clear and informative validation messages for the various fields accepted. Specifically, the validation for certain fields is not transparent, leading to confusion and frustration during integration.
Example:
Consider a scenario where a software system sets its testing environment with user emails in the format [email protected]. If the sandbox of Iyzipay cannot accept this format, the service needs to raise a validation error related to this specific field. However, in the current version, the service returns an error message stating "invalid signature," which is unclear and does not provide sufficient information about the root cause of the issue.
Request:
I request that the validation mechanism for the initialization of the payment form be revisited and improved to provide more explicit and user-friendly error messages. This enhancement will greatly benefit developers integrating with Iyzipay by reducing the time spent diagnosing issues and ensuring a smoother overall experience.
Expected Outcome:
Clear and specific validation messages for each field, highlighting the nature of the error.
Informative responses that guide developers in resolving issues efficiently.
Improved documentation regarding field-specific validation requirements.
Steps to Reproduce:
Thank you for your attention to this matter, and I appreciate your efforts in continuously improving the Iyzipay payment service.
The text was updated successfully, but these errors were encountered: