arkayan_sarkar
TPToss payments 개발자 커뮤니티
•Created by Ali on 2/1/2025 in #🌎┃global-support
Need help
No I did not receive the redirect request
107 replies
TPToss payments 개발자 커뮤니티
•Created by Ali on 2/1/2025 in #🌎┃global-support
Need help
@유부장 @냥과장 @토스페이먼츠 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.
107 replies
TPToss payments 개발자 커뮤니티
•Created by Ali on 2/1/2025 in #🌎┃global-support
Need help
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)
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)
107 replies
TPToss payments 개발자 커뮤니티
•Created by Ali on 2/1/2025 in #🌎┃global-support
Need help
📌 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.
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.
107 replies
TPToss payments 개발자 커뮤니티
•Created by Ali on 2/1/2025 in #🌎┃global-support
Need help
It’s silly to ask if we have an internet connection.
107 replies
TPToss payments 개발자 커뮤니티
•Created by Ali on 2/1/2025 in #🌎┃global-support
Need help
@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.
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.
107 replies
TPToss payments 개발자 커뮤니티
•Created by Ali on 2/1/2025 in #🌎┃global-support
Need help
@유부장 @냥과장
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.
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.
107 replies
TPToss payments 개발자 커뮤니티
•Created by Ali on 2/1/2025 in #🌎┃global-support
Need help
@냥과장 @유부장 @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.
- 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.
107 replies
TPToss payments 개발자 커뮤니티
•Created by Ali on 2/1/2025 in #🌎┃global-support
Need help
@냥과장 @Ayaan이안 @유부장
4. We Have Provided All Requested Logs & Proofs
- We shared the exact console errors that occur inside WebView.
- 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.
- 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.
107 replies
TPToss payments 개발자 커뮤니티
•Created by Ali on 2/1/2025 in #🌎┃global-support
Need help
@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:
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.
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."
107 replies
TPToss payments 개발자 커뮤니티
•Created by Ali on 2/1/2025 in #🌎┃global-support
Need help
Kindly solve the issue as soon as possible.
107 replies
TPToss payments 개발자 커뮤니티
•Created by Ali on 2/1/2025 in #🌎┃global-support
Need help
I told you so many times. We have it set in the source code.
107 replies
TPToss payments 개발자 커뮤니티
•Created by Ali on 2/1/2025 in #🌎┃global-support
Need help
It's okay. I can understand.
107 replies
TPToss payments 개발자 커뮤니티
•Created by Ali on 2/1/2025 in #🌎┃global-support
Need help
We need support from official Tosspayment Brandpay's technical support team. Not from any third party. Thank you.
107 replies
TPToss payments 개발자 커뮤니티
•Created by Ali on 2/1/2025 in #🌎┃global-support
Need help
@Ayaan이안 @유부장 any updates please?
107 replies
TPToss payments 개발자 커뮤니티
•Created by Ali on 2/1/2025 in #🌎┃global-support
Need help
@유부장 if there is any solution for webview_flutter
107 replies