Closed Unequaled804 closed 11 months ago
Hi @Unequaled804 ,
Can you add the onError
callback to your implementation and verify if you get any errors there?
Are you using the Advanced or Sessions flow? Can you see the /payments request happening when the Pay button is clicked?
Hi @Unequaled804 ,
Can you add the
onError
callback to your implementation and verify if you get any errors there? Are you using the Advanced or Sessions flow? Can you see the /payments request happening when the Pay button is clicked?
Hi @ribeiroguilherme
Thank you for your reply.
onError
callback.Hi @Unequaled804 ,
When requesting the payment methods from the Backend (during the /paymentMethods
call), do you get applepay
as part of the paymentMethods
list? Does it contain the configuration field with merchantId
and merchantName
?
Regarding the Testing cards, are you using any of the test cards listed here ?
I see that you are also loading apple-pay-sdk.js
- what is that? I don't think our library loads such external SDK. It uses what is already available within Safari
Hi @Unequaled804 ,
When requesting the payment methods from the Backend (during the
/paymentMethods
call), do you getapplepay
as part of thepaymentMethods
list? Does it contain the configuration field withmerchantId
andmerchantName
?Regarding the Testing cards, are you using any of the test cards listed here ?
I see that you are also loading
apple-pay-sdk.js
- what is that? I don't think our library loads such external SDK. It uses what is already available within Safari
Hi @ribeiroguilherme ,
merchantId
and merchantName
.const configuration = {
// other config...
paymentMethodsResponse: {
paymentMethods: [
{
brands: ['amex', 'diners', 'discover', 'jcb', 'mc', 'visa'],
name: 'Credit Card',
type: 'scheme',
},
{
brands: ['amex', 'discover', 'jcb', 'mc', 'visa'],
configuration: {
merchantId: '000000XXXXXXXXX',
merchantName: 'XXXXXX_TEST1247XXXXX',
},
name: 'Apple Pay',
type: 'applepay',
},
{
name: 'BENEFIT',
type: 'benefit',
},
{
name: 'Bank Transfer',
type: 'kcp_banktransfer',
},
{
name: 'Korea–issued cards',
type: 'kcp_creditcard',
},
{
name: 'KNet',
type: 'knet',
},
{
name: 'UnionPay',
type: 'unionpay',
},
],
},
// other config...
}
We are using a Sandbox Apple ID and some testing cards provided by the Apple official website, which is the same link you mentioned earlier, for testing purposes.
The apple-pay-sdk.js
was imported for API-only integration. However, the payment flow could not proceed due to an unknown error. As a result, we decided to switch to the Web Component integration.
We tried removing the imported apple-pay-sdk.js
script to avoid potential conflicts, but the issue still persists.
Hi @Unequaled804 ,
It seems like everything is correct.
Can you try to do a payment on https://mystoredemo.io to double check that your testing card works? Do you have by any chance a live testing website where I could take a look?
Update:
I tested your implementation, and it worked well if my testing cards. It could be that your testing device with the Cards are not set up correctly. Please follow up this with the assigned implementation manager. Cheers!
Describe the bug When integrating Apple Pay through Adyen Web Component, the prompt "Payment Not Completed" appears and there is no error information in the console.
To Reproduce Steps to reproduce the behavior:
Expected behavior Apple Pay payment should succeed or prompt a payment failure, and the console should display detailed error information
Smartphone (please complete the following information):
Additional context There are no error messages or other output in the Safari console when the payment error occurs. The methods onSubmit, onConfigSuccess, onLoad, onChange, onBinValue, onAdditionalDetails, onValidateMerchant, and onAuthorized are all configured in the configuration, but they do not seem to be triggered.
I would like to ask how to troubleshoot and handle this issue?
Thank you very much!