Need help
Hi sir Subject: Request for TossPayments Sandbox Credentials & WebView Checkout Issue
Dear TossPayments BrandPay Support Team,
We have integrated the TossPayments BrandPay WooCommerce Payment Gateway Plugin on our e-commerce website, and it is working perfectly on desktop browsers. However, we are facing an issue when processing payments through WebView checkout in our mobile app.
Issue Details:
When users attempt to complete a payment inside the WebView, they receive the following error message:
Checkout
An error occurred
[BRIDGE] Request Timeout. id: K1_OZ-XWxenk09yuJ01GY, type: TOSSPAYMENTSREQUEST_RESPONSE,
body: {"step":"TOSSPAYMENTSREQUEST","requestName":"GET_PARAMETER","payload": {"name":"customerToken"}}
This error only occurs inside WebView checkout in our Mobile app. The payment gateway is functioning correctly on desktop browsers. Request: To debug and resolve this issue, please provide us with the following sandbox (test) credentials: ✅ Test API Keys (Client Key & Secret Key) ✅ Test Card Details for debugging payments ✅ Any Additional Configuration or Settings Required for WebView Compatibility Please guide us on how to enable the test environment or any additional steps needed to fix this issue. Looking forward to your support. Best Regards, Ali Nawazish Elite international
An error occurred
[BRIDGE] Request Timeout. id: K1_OZ-XWxenk09yuJ01GY, type: TOSSPAYMENTSREQUEST_RESPONSE,
body: {"step":"TOSSPAYMENTSREQUEST","requestName":"GET_PARAMETER","payload": {"name":"customerToken"}}
This error only occurs inside WebView checkout in our Mobile app. The payment gateway is functioning correctly on desktop browsers. Request: To debug and resolve this issue, please provide us with the following sandbox (test) credentials: ✅ Test API Keys (Client Key & Secret Key) ✅ Test Card Details for debugging payments ✅ Any Additional Configuration or Settings Required for WebView Compatibility Please guide us on how to enable the test environment or any additional steps needed to fix this issue. Looking forward to your support. Best Regards, Ali Nawazish Elite international
63 Replies
⏳ 잠시만 기다려주세요! 곧 답변드리겠습니다
오류 문의일 경우 아래 정보를 미리 전달해주시면, 빠른 답변에 도움이 됩니다.
- 주문번호(orderId) :
- 문의 내용 :
(img를 함께 첨부해주시면 도움이됩니다)
* 계약관련 내용은 1544-7772로 문의주세요.
* 주말/공휴일에는 답변이 늦을 수 있어요.
Hi @Ali, thank you to contacting us.
1. Test API Keys: You can find your test API key on this website: https://developers.tosspayments.com/my/api-keys -> Select your merchant in the left navigation bar. Make sure your MID starts with cp_.
2. Test Card Details: We do not provide test card details. Please use your actual card. You may need to contact your Korean colleagues for this.
3. Check the Korean documentation for WebView support.
https://docs.tosspayments.com/guides/v2/webview
Also make sure your firewall is properly open and doesn't restrict the domain of the WebView (otherwise it won't work properly).
https://docs.tosspayments.com/reference/using-api/security - Seriously refer to the "브랜드페이 방화벽 설정 / BrandPay Firewall Settings" section.
You may need to use Google Translate or get help from a Korean colleague to read both documents, as they are only available in Korean.
Also, please share the MID or client key you used on the website to further check the logs on Toss Payments side or for follow-up actions.
I cannot find TossPayments BrandPay WooCommerce Payment Gateway Plugin in WooCommerce market place.
As far as I know, WooCommerce does not support BrandPay as a plugin.
What is the exact plugin name you are using?
If I remember correctly, they made the plugin by themselves
Google Docs
I have a question I would like them to answer
I have a question I would like them to answer. Error: I/chromium( 5963): [INFO:CONSOLE(1287)] “Refused to apply style from ‘Checkout – 11mart’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.”, source: Checkout – 11mart (1287) I am ...
Are you integrating with Brandpay using WooCommerce plugin, aren't you?
in this case you cannot use our flutter pluin, you need to just using webview to integrate it not Tosspayments native SDK
Google Docs
We use the payment gateway API & SDK to create “woo-toss-brandpay
We use the payment gateway API & SDK to create “woo-toss-brandpay.zip =>”. But when using webview on mobile, we cannot open this form.
Hi @Ali @arkayan_sarkar, Can you confirm you can open the payment window (which you attached the screenshot in the Word doc) in the Mobile Chrome browser?
I used Mobile Chrome browser.And it works.But when using flutter webview it doesn’t work.
In Mobile, the page will appear as pop-up. Please double check your webview works well with popup
We have supported most payment gateways with popup worldwide. Like VNPAY Gateway, PayStack Gateway, PayTabs Gateway, Myfatoorah Gateway, Mercado Pago and Pagseguro, PayFast, Flutterwave, Stripe, Razorpay, PayU, Authorize.net, 2Checkout, Xendit, Midtrans, PayPal, Wallet, HyperPay, Cashfree, Tabby, Iyzico, Paytm Gateway etc. But this payment gateway we have problem.
If you have example of flutter webview when using to popup payment form then please share the example source code
Let me check there's any example / sample source code.
Please help, Waiting...
@arkayan_sarkar I am still actively finding any reference for this issue.
Can you provide us what error are you seeing? Or there's no error and just screen freeses?
And this is the sample code with Toss SDK.
https://github.com/youjun-lee/flutter_webview_sample_app
You can refer this and adopt to your use case as this source code provides the way with Webview.
However, your use case is Brandpay so you might not need to handle custom scheme and Toss SDK.
Google Docs
this is the error code returned by Webview flutter
this is the error code returned by Webview flutter in the reference example i also don’t see any special settings for webview flutter.
Yes as you're integrating the Brandpay, it should not have a huge special settings for the webview.
As the image quality is low, I cannot read the error message; can you copy as text into this chat?
@arkayan_sarkar
I can see "알 수 없는 에러가 발생했습니다" coming from Promise, right?
I/chromium( 7437): [INFO: CONSOLE(1362)] "Uncaught (in promise) Error: An unknown error occurred.", source: https://www.11martkorea.com/checkout-2/order-pay/14214/?key=wc_order_vCK93AQouBEkN (1362)
Please share your orderId / MID to check the logs from Toss side. I guess the error thrown from the Toss server somehow
This image will help your support team to See the problem more clearly
https://drive.google.com/file/d/1Gh7_l147Y8xDkmhPQzbr6ojpZVKdXgA0/view?usp=sharing
Google Docs
toss.png
Thx. As I dont have a permission to retrieve the logs, Toss Team will respond you as soon as they can.
cc @냥과장 Please check the logs for them, as they're experiencing 500 error from toss side when loading the brandpay window
Cloud you check what is the exact error "I/chromium( 7437): [INFO: CONSOLE(1362)] "Uncaught (in promise) Error: An unknown error occurred.", source: https://www.11martkorea.com/checkout-2/order-pay/14214/?key=wc_order_vCK93AQouBEkN "?
based on our log, I cannot find any errors.
and I have tested in your site and it works properly.
@냥과장 I believe you are not taking this issue seriously or making an effort to resolve it. Have you thoroughly checked the scenario? I kindly request you to review all the previous messages from the beginning. We all know it works perfectly, except in WebView.
Oh I see, does it only have an issue on webview?
@냥과장 Yes
based on our log we did not response any errors.
so we need to investigate why you got the error (알 수 없는 에러가 발생했습니다)
Could you check the webview console?
I will also share the information to brand pay dev team to investigate it.
Hi @Stevie @seoulwebdesign ,
Seems the user goes through WooCommerce for the brandpay integration,
And we believe that you can help us some more details on this plug in.
Could you kindly help us to provide some information regarding the error facing here?
Hi @arkayan_sarkar ,
Just in case, please check below
1) WebView JavaScript enablement
WebView(
initialUrl: "https://your-payment-url.com",
javascriptMode: JavascriptMode.unrestricted, // Ensures JavaScript is enabled
)
AOS
webView.getSettings().setJavaScriptEnabled(true);
webView.getSettings().setDomStorageEnabled(true);
iOS
let webViewConfiguration = WKWebViewConfiguration()
webViewConfiguration.preferences.javaScriptEnabled = true
let webView = WKWebView(frame: .zero, configuration: webViewConfiguration)
2) CORS
webView.getSettings().setMixedContentMode(WebSettings.MIXED_CONTENT_ALWAYS_ALLOW);
allowsInsecureConnections
Stevie's post is somewhere else, so would it be better to post it https://discord.com/channels/864296203746803753/1315818319995080775 here or on another post?
@유부장 if there is any solution for webview_flutter
Hello @Ayaan이안 sorry i did not make this plugin 🙂
we do magento ones seoulcommerce.com
but i might be able to help the op can message me directly or email stevie@seoulcommerce.com
@Ayaan이안 @유부장 any updates please?
We need support from official Tosspayment Brandpay's technical support team. Not from any third party. Thank you.
Sorry today is the weekend in Korea and it is out of the business hours. We will get back to you on Monday.
Okay
Please be aware that we operate the service in GMT+9 timezone
It's okay. I can understand.
@arkayan_sarkar did you try it with your website?
And it is for the webview_flutter
controller = WebViewController()
..setJavaScriptMode(JavaScriptMode.unrestricted)
Addtionally, please check the webview console error, first
I told you so many times. We have it set in the source code.
Why this error occurs?
Kindly solve the issue as soon as possible.
I would like to make sure one thing.
You are using WooCommerce platform.
You did not integrated Tosspayments Brandpay "DIRECTLY", but you have integrated product via "3rd PARTY" plugin.
In this case, we cannot provide clear soluton for you.
Because, we do not know how the "3rd PARTY" plugin is working, especially in several special cases.
You have to raise your question to WooCommerce platform, not Tosspayments directly.
We can provide clear solution for the merchant when the merchant integrating the Tosspaymennt product via "Tosspayments provided" product.
Please raise your question to WooCommerce platform side.
if WooCommerce platform side find out issue, then they will raise the question to us.
@Ayaan이안 @냥과장
Subject: Re: TossPayments WebView Issue – Clarification & Next Steps
Dear [TossPayments Support Team],
I would like to address the inconsistencies in your responses and seek a clear resolution to the WebView issue we are facing.
1. The Issue is Not with WooCommerce - The payment works perfectly on normal browsers, but fails inside WebView due to a request timeout.
- This clearly indicates that the issue is on TossPayments' side, not WooCommerce.
- WooCommerce has no control over WebView behavior.
2. Redirecting to WooCommerce is Not a Solution - TossPayments has already confirmed that the payment works on our website and even provided a screenshot as proof (냥과장 — 2/14/25, 3:46 PM).
- If the payment was truly a WooCommerce issue, it wouldn’t work in normal browsers either.
- TossPayments previously advised us to check the WebView console logs, which we did, and we shared the errors with you.
- Instead of resolving the issue, you are now saying to contact WooCommerce, which is irrelevant.
3. TossPayments Previously Acknowledged the Issue - On 2/14/25, 5:05 PM, TossPayments responded:
- The error clearly shows a TossPayments API timeout.
- Instead of addressing the logs, you are now saying, "We don’t know how third-party plugins work."
- If that was the case, then why did TossPayments initially confirm the issue and say they would investigate it?
5. Third-Party Plugin Still Uses TossPayments API - Even though we are using a third-party plugin, it still sends API requests directly to TossPayments exactly as per your documentation.
- The request is correct, but TossPayments returns a timeout error inside WebView.
- Since TossPayments controls the API behavior, your technical team is responsible for debugging this issue.
- Unlike international payment gateways such as PayPal, Stripe, Razorpay, and others, TossPayments does not provide an official plugin for WooCommerce.
- Because of this, merchants must rely on third-party plugins to integrate TossPayments, but that does not remove TossPayments’ responsibility for ensuring that its API functions correctly in all environments. @냥과장 @유부장 @Ayaan이안 6. TossPayments API Should Work in All Environments - TossPayments is a payment gateway, and its API should be fully functional regardless of whether it is accessed through a browser or WebView.
- Other major payment gateways, such as Stripe, PayPal, and Razorpay, do not have these issues in WebView environments.
- If TossPayments does not function properly in WebView, it is a technical limitation on TossPayments' side, and your team needs to investigate and resolve it.
Next Steps & Request for Resolution - Instead of redirecting us to WooCommerce (which is completely irrelevant in this case), please properly investigate the WebView issue and provide a solution.
- TossPayments previously confirmed that they would escalate the issue to the Brand Pay dev team. What is the current update on that?
- We expect a proper technical resolution, not just an attempt to shift responsibility. @유부장 @냥과장
Please note that I am representing my client, @Ali teinternational1199, who is a direct merchant using TossPayments. My client has paid for both the TossPayments gateway and additional BrandPay services. @Ayaan이안 @토스페이먼츠 BOT
Since this issue directly affects a paying TossPayments merchant, we expect proper support and a clear resolution instead of being redirected elsewhere. Please provide a solution accordingly.
Dear [TossPayments Support Team],
I would like to address the inconsistencies in your responses and seek a clear resolution to the WebView issue we are facing.
1. The Issue is Not with WooCommerce - The payment works perfectly on normal browsers, but fails inside WebView due to a request timeout.
- This clearly indicates that the issue is on TossPayments' side, not WooCommerce.
- WooCommerce has no control over WebView behavior.
2. Redirecting to WooCommerce is Not a Solution - TossPayments has already confirmed that the payment works on our website and even provided a screenshot as proof (냥과장 — 2/14/25, 3:46 PM).
- If the payment was truly a WooCommerce issue, it wouldn’t work in normal browsers either.
- TossPayments previously advised us to check the WebView console logs, which we did, and we shared the errors with you.
- Instead of resolving the issue, you are now saying to contact WooCommerce, which is irrelevant.
3. TossPayments Previously Acknowledged the Issue - On 2/14/25, 5:05 PM, TossPayments responded:
"Based on our log, we did not respond with any errors.- Now, instead of actually investigating, you are ignoring your previous response and trying to shift responsibility elsewhere. @냥과장 @Ayaan이안 @유부장 4. We Have Provided All Requested Logs & Proofs - We shared the exact console errors that occur inside WebView.
So we need to investigate why you got the error (알 수 없는 에러가 발생했습니다).
Could you check the WebView console?
I will also share the information with the Brand Pay dev team to investigate it."
- The error clearly shows a TossPayments API timeout.
- Instead of addressing the logs, you are now saying, "We don’t know how third-party plugins work."
- If that was the case, then why did TossPayments initially confirm the issue and say they would investigate it?
5. Third-Party Plugin Still Uses TossPayments API - Even though we are using a third-party plugin, it still sends API requests directly to TossPayments exactly as per your documentation.
- The request is correct, but TossPayments returns a timeout error inside WebView.
- Since TossPayments controls the API behavior, your technical team is responsible for debugging this issue.
- Unlike international payment gateways such as PayPal, Stripe, Razorpay, and others, TossPayments does not provide an official plugin for WooCommerce.
- Because of this, merchants must rely on third-party plugins to integrate TossPayments, but that does not remove TossPayments’ responsibility for ensuring that its API functions correctly in all environments. @냥과장 @유부장 @Ayaan이안 6. TossPayments API Should Work in All Environments - TossPayments is a payment gateway, and its API should be fully functional regardless of whether it is accessed through a browser or WebView.
- Other major payment gateways, such as Stripe, PayPal, and Razorpay, do not have these issues in WebView environments.
- If TossPayments does not function properly in WebView, it is a technical limitation on TossPayments' side, and your team needs to investigate and resolve it.
Next Steps & Request for Resolution - Instead of redirecting us to WooCommerce (which is completely irrelevant in this case), please properly investigate the WebView issue and provide a solution.
- TossPayments previously confirmed that they would escalate the issue to the Brand Pay dev team. What is the current update on that?
- We expect a proper technical resolution, not just an attempt to shift responsibility. @유부장 @냥과장
Please note that I am representing my client, @Ali teinternational1199, who is a direct merchant using TossPayments. My client has paid for both the TossPayments gateway and additional BrandPay services. @Ayaan이안 @토스페이먼츠 BOT
Since this issue directly affects a paying TossPayments merchant, we expect proper support and a clear resolution instead of being redirected elsewhere. Please provide a solution accordingly.
No. Sorry for this.
We do not know it is WooCommerce issue or not.
We have webview guideline as below link.
https://docs.tosspayments.com/guides/v2/webview
Redirecting to WooCommerce is the only solution for now.
I am sorry to hear that other payment service provider do not have issues.
Again,
WooCommerce plugin "IS NOT" official plugin from Tosspayments.
Means that it is belongs to "3rd party" method.
I believe you understand what "3rd party" method meaning here.
Please raise your question to WooCommerce plugin side first.
If you have integrated Tosspayments solution "DIRECTLY"
then surely yes, we have responsility to support you.
No matter what kind of issue you facing, we need to find the solution for you.
https://docs.tosspayments.com/guides/v2/get-started
But, your client is using "WooCommerce plugin".
You should know what is the technical meaning of using "3rd party plugin" here.
Merchant - WooCommerce plugin - Tosspayments
We are sorry that there is no official method to integrate Tosspayments via provided WooCommerce plugin.
We will consider it, but not now.
And more, mobile app webview is mostly belongs to "merchant configuration".
Because, mostly, merchant is the one who develop the mobile app for themselves.
Please raise your question to WooCommerce plugin side first.
If you have further question,
Please let us know via techsupport@tosspayments.com
@arkayan_sarkar and this issue is a netowrk connection issue your webview cannot connect our server anyway that the prcess was not succeeded.
also I told many time, you need to provide the webview console, not flutter console. because all these error in the webview and javascript side.So your flutter webview console message is not enough information to investigate it.
So please check the webview console errors and check any connection failures are shown in webview.
Here is the console showing all the errors and we use webview_flutter package of Flutter
I was wondering which webview console you want me to provide. While we use webview_flutter package
It’s silly to ask if we have an internet connection.
Ok we are also investigating this issue. I will let you know the result.
@arkayan_sarkar please check one thing. when you open the brandpay UI, did you get a request to redirectURL.
This error is because AccessToken is not issued that means redirectURL is not called properly.
📌 Re: TossPayments Flutter WebView Issue – Clarification Required
Dear @유부장, @냥과장, and TossPayments Support Team,
Thank you for your response. However, I would like to clarify a few points regarding the issue:
1️⃣ TossPayments' Responsibility Towards Merchants While I understand that the WooCommerce plugin is not officially provided by TossPayments, my client (@Ali) is a directly paying merchant of TossPayments and has also purchased additional BrandPay services.
👉 Regardless of the integration method, TossPayments is still responsible for ensuring its API functions correctly within any implementation scenarios. 2️⃣ The Issue is NOT with WooCommerce The error "알 수 없는 에러가 발생했습니다" (Unknown error occurred) is coming from TossPayments' API, not WooCommerce.
- The TossPayments API is failing in Flutter WebView, not the WooCommerce plugin.
- If this were a WooCommerce issue, other payment gateways (PayPal, Stripe, Razorpay, etc.) would also fail in the same setup – but they do not.
- Our WooCommerce plugin works perfectly in any browser (Chrome, Firefox, Edge, Safari, etc.), mobile browsers, and normal website environments.
- The only place it fails is inside Flutter WebView, which means the issue lies with TossPayments' API response to WebView requests, not our integration.
3️⃣ Redirecting to WooCommerce is NOT a Solution Saying that "redirecting to WooCommerce is the only solution for now" is not an acceptable answer.
- Other international payment providers allow Flutter WebView payments without forcing redirections.
- If TossPayments has limitations with Flutter WebView transactions, this should be explicitly documented in your API guidelines, along with an official solution. 4️⃣ Flutter WebView Console Log Request I understand that you require the Flutter WebView console logs instead of Flutter logs.
I will collect and provide those logs for further investigation.
However, based on your own response, you confirmed that the issue is a network connection failure from Flutter WebView to TossPayments' servers.
📌 This further supports the point that the problem is not with WooCommerce but rather with how TossPayments' API is handling Flutter WebView requests.
5️⃣ Lack of an Official WooCommerce Plugin is a Business Limitation Unlike PayPal, Stripe, Razorpay, etc., TossPayments does not provide an official WooCommerce plugin.
This forces merchants to rely on third-party plugins, which TossPayments then refuses to support.
👉 If TossPayments does not want to provide direct support for these cases, then an official WooCommerce plugin should be developed to avoid such issues in the future.
6️⃣ Next Steps – Expectation from TossPayments To move forward, we need TossPayments to:
✅ Clarify whether Flutter WebView-based payments are officially supported and, if so, provide proper documentation or fixes.
✅ Investigate why TossPayments' API is returning an unknown error in Flutter WebView, even when the implementation follows standard API guidelines.
✅ Confirm if there are any known Flutter WebView limitations on TossPayments' side, as other payment providers do not have this issue.
Since this is a direct merchant issue, we expect proper technical support from TossPayments instead of being redirected to third parties.
Looking forward to your response.
Best regards,
@arkayan_sarkar (On behalf of @Ali)
Dear @유부장, @냥과장, and TossPayments Support Team,
Thank you for your response. However, I would like to clarify a few points regarding the issue:
1️⃣ TossPayments' Responsibility Towards Merchants While I understand that the WooCommerce plugin is not officially provided by TossPayments, my client (@Ali) is a directly paying merchant of TossPayments and has also purchased additional BrandPay services.
👉 Regardless of the integration method, TossPayments is still responsible for ensuring its API functions correctly within any implementation scenarios. 2️⃣ The Issue is NOT with WooCommerce The error "알 수 없는 에러가 발생했습니다" (Unknown error occurred) is coming from TossPayments' API, not WooCommerce.
- The TossPayments API is failing in Flutter WebView, not the WooCommerce plugin.
- If this were a WooCommerce issue, other payment gateways (PayPal, Stripe, Razorpay, etc.) would also fail in the same setup – but they do not.
- Our WooCommerce plugin works perfectly in any browser (Chrome, Firefox, Edge, Safari, etc.), mobile browsers, and normal website environments.
- The only place it fails is inside Flutter WebView, which means the issue lies with TossPayments' API response to WebView requests, not our integration.
3️⃣ Redirecting to WooCommerce is NOT a Solution Saying that "redirecting to WooCommerce is the only solution for now" is not an acceptable answer.
- Other international payment providers allow Flutter WebView payments without forcing redirections.
- If TossPayments has limitations with Flutter WebView transactions, this should be explicitly documented in your API guidelines, along with an official solution. 4️⃣ Flutter WebView Console Log Request I understand that you require the Flutter WebView console logs instead of Flutter logs.
I will collect and provide those logs for further investigation.
However, based on your own response, you confirmed that the issue is a network connection failure from Flutter WebView to TossPayments' servers.
📌 This further supports the point that the problem is not with WooCommerce but rather with how TossPayments' API is handling Flutter WebView requests.
5️⃣ Lack of an Official WooCommerce Plugin is a Business Limitation Unlike PayPal, Stripe, Razorpay, etc., TossPayments does not provide an official WooCommerce plugin.
This forces merchants to rely on third-party plugins, which TossPayments then refuses to support.
👉 If TossPayments does not want to provide direct support for these cases, then an official WooCommerce plugin should be developed to avoid such issues in the future.
6️⃣ Next Steps – Expectation from TossPayments To move forward, we need TossPayments to:
✅ Clarify whether Flutter WebView-based payments are officially supported and, if so, provide proper documentation or fixes.
✅ Investigate why TossPayments' API is returning an unknown error in Flutter WebView, even when the implementation follows standard API guidelines.
✅ Confirm if there are any known Flutter WebView limitations on TossPayments' side, as other payment providers do not have this issue.
Since this is a direct merchant issue, we expect proper technical support from TossPayments instead of being redirected to third parties.
Looking forward to your response.
Best regards,
@arkayan_sarkar (On behalf of @Ali)
Please do not use GPT, we need information below
what is MID (Merchant ID) or API Key that you are using
As Tosspayments prospective, IT IS NOT direct merchant issue
GPT is answering wrong information.
what is MID (Merchant ID) or API Key that you are using
@유부장 @냥과장 @토스페이먼츠 BOT
I want to clarify that my responses are based on TossPayments' own documentation and logical technical analysis—not AI-generated. The concerns I raised remain valid, and avoiding them by blaming AI is not a technical resolution.
🔹 Merchant Information:
- MID (Merchant ID): cp_11martqz7u - API Key: live_ck_Gv6LjeKD8aPRXL62EmjwrwYxAdXy
🚨 Clarification on "Direct Merchant Issue"
My client (@Ali) is a direct paying TossPayments merchant and has also purchased additional BrandPay services. The payment process failure is occurring within TossPayments' API in WebView, which means this is directly related to TossPayments' service, not WooCommerce.
❓ Unanswered Technical Questions
Despite multiple responses, the following concerns remain unanswered:
1️⃣ Why does TossPayments' API fail in WebView while other payment gateways (PayPal, Stripe, Razorpay, etc.) work fine in the same setup?
2️⃣ Why is TossPayments’ own system returning an "Unknown Error" (
3️⃣ If WebView-based payments are officially unsupported, why is this not explicitly stated in your documentation?
⚠️ Please focus on resolving the technical issue instead of dismissing valid concerns. We expect clear answers and proper support for a paying merchant.
Looking forward to a constructive response.
I want to clarify that my responses are based on TossPayments' own documentation and logical technical analysis—not AI-generated. The concerns I raised remain valid, and avoiding them by blaming AI is not a technical resolution.
🔹 Merchant Information:
- MID (Merchant ID): cp_11martqz7u - API Key: live_ck_Gv6LjeKD8aPRXL62EmjwrwYxAdXy
🚨 Clarification on "Direct Merchant Issue"
My client (@Ali) is a direct paying TossPayments merchant and has also purchased additional BrandPay services. The payment process failure is occurring within TossPayments' API in WebView, which means this is directly related to TossPayments' service, not WooCommerce.
❓ Unanswered Technical Questions
Despite multiple responses, the following concerns remain unanswered:
1️⃣ Why does TossPayments' API fail in WebView while other payment gateways (PayPal, Stripe, Razorpay, etc.) work fine in the same setup?
2️⃣ Why is TossPayments’ own system returning an "Unknown Error" (
알 수 없는 에러가 발생했습니다) instead of providing a clear API response?3️⃣ If WebView-based payments are officially unsupported, why is this not explicitly stated in your documentation?
⚠️ Please focus on resolving the technical issue instead of dismissing valid concerns. We expect clear answers and proper support for a paying merchant.
Looking forward to a constructive response.
GPT need to understand what is 3rd party plugin meaning.
No I did not receive the redirect request
in this case, the redirection url (https://www.11martkorea.com/wp-admin/admin-post.php?action=toss_wc_webhook) is not working in you webview.
Could you check some settings to prevent to move unauthorized url or redirect inside of iframe in your webview ?
In our log, I can find some logs to try to redirect https://www.11martkorea.com/wp-admin/admin-post.php in mobile devices but I am not sure it was web browser or webview, please try to reproduce this error and let us know the customerkey and exact time you tryt
Order created at 8:45 GMT+7
I have found several logs to request call the redirectURL like this at 8:45 GMT+7
{"authorizationUrl":"https://www.11martkorea.com/wp-admin/admin-post.php?action=toss_auth_webhook&code=DJaYngrojjdvQ4a7JyVezGdR&customerKey=Tntoan2515_gmail_comBr3T","expiresIn":300,"customerAuthCode":"XXXXXX"}
but we did not get any request for AccessToken.
so please check you also did not get any request to https://www.11martkorea.com/wp-admin/admin-post.php?action=toss_auth_webhook&code=DJaYngrojjdvQ4a7JyVezGdR&customerKey=Tntoan2515_gmail_comBr3T
and if did not, I believe this request was blocked your webview because of some reasons.
Also in this thread Ayaan already recomment to test with our sample flutter app ( https://github.com/youjun-lee/flutter_webview_sample_app )
Have you tried it with your web site? and Did you got same issue on that?
GitHub
GitHub - youjun-lee/flutter_webview_sample_app: flutter webview sample
flutter webview sample. Contribute to youjun-lee/flutter_webview_sample_app development by creating an account on GitHub.