-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Visa will require 5 data elements in the 3DS Authentication Request (AReq)-Mobile app #499
Comments
Hey @atalleb This is not necessary for native 3DS2. You can see list of necessary fields in Make a payment doc. You can use |
We have following queries on 3DS native, Please clarify.
|
Hey @atalleb Note We recommend using Native 3DS2 for mobile apps.
If something is opening in a SFViewController or Android Custom Tabs - then it is a Redirect 3DS2, not a Native 3DS2.
No. DropIn will simplify your integration, but your backend is still controlling the payment flow and communication with Adyen API.
BrowserInfo Are you on |
We are under DropIn Flow where we are appearing payment component with start(payment-type) in React native. But in case of save payment flow for debit/credit visa and if authentication required by Adyen for that we are using WebView screen to determine the request link Like it’s contains adyencheckout://, adyenreactnative:// etc. then we are showing success popup based on that. Please confirm in this case we have to pass browserinfo width and height or not. |
Sorry @atalleb |
Can you please clarify below 2 points.
import { CheckoutAPI, Client } from '@adyen/api-library'; for other payment like PayPal, sepa, etc based on backend action we are using nativeComponent.handle because in save payment flow we are not using start(payment-type) right? and not opening any popup to enter info.
|
As already mention4ed above -
We have example code for stored payment methods. You don't have to handle any actions yourself, you can use import { AdyenAction } from '@adyen/react-native';
await AdyenAction.handle(action, configuration) |
@descorp ,implemented like as you suggested, observed one time popup is being opened in browser by AdyenAction but main concern is it's payment happened without any card holder approval? Can you please suggest in which case it does not ask for approval, earlier it was working perfectly with 1.2.0 version but with the latest version looks payment done without any approval in case of save payment card.Please clarify. |
Hey @atalleb
Those two statements contradict each other. If you have provided card details (or stored card details) and have received and
Depending on issuer of the card, country, fraud score etc. Our Test cards provides examples for different kind of a flows. In general - always recommend to use native threeDS with paymentMethod.threeDS2SdkVersion and
If you want to have abetter understanding of 3D Secure - please check documentation. |
Checked for UK card. |
@descorp We are using @adyen/react-native": "1.2.0", in this case how we can redirect the action in the case if save payment flow, can you please suggest. AdyenAction is in latest version correct? |
It is available from 2.0.0 indeed. In general 1.2.0 does not provide PrivacyManifest for iOS - we recommend to update to at least 1.2.1 |
@descorp with 1.2.1 how we can handle payment redirection in the case of save card? we need to use web view stuff or any other official way to handle that. |
Fair. There is no officially recommended way of handling actions for v1 in API-only (or CSE) integration. I can only advice you to upgrade to v2. The Migration process should not be very complicated. |
Merchants must provide complete and accurate transaction data in their authentication request for accurate risk assessments and better performance.
This is an update of the article shared on November 22th, where initially Visa required 12 fields in the authentication message with an effective date of February 2024. After feedback and discussions with Visa product teams, they now revised the bulletin, reducing the number of fields required and postponing the effective date.
The mandatory fields are now as follows:
1.Browser screen height
2.Browser screen width
3.Browser IP address
4.Cardholder Name
5.Cardholder Email Address OR Cardholder Phone Number
Query 1:
In case of 3DS flow we open in app browser for validating the request so in this case do we need to pass browser width and height
if we have to pass then please let us know on which point we should pass these values to Adyen.
The text was updated successfully, but these errors were encountered: