73 Replies
⏳ 잠시만 기다려주세요! 곧 답변드리겠습니다
오류 문의일 경우 아래 정보를 미리 전달해주시면, 빠른 답변에 도움이 됩니다.
- 주문번호(orderId) :
- 문의 내용 :
(img를 함께 첨부해주시면 도움이됩니다)
* 계약관련 내용은 1544-7772로 문의주세요.
* 주말/공휴일에는 답변이 늦을 수 있어요.
확인중입니다
넵 알겠습니다
@Giwon 확인이 좀 늦어졌네요
지금 시도 가능하실까요?
제가 직접 귀사 상점 테스트키로 빌링키 발급까지 성공했습니다
잠시만요 개발자도 초대하겠습니다
@henilkevadiya
Hello
I will check it now
Lets check this
{
"code": "ERROR_WITH_MERT_PAGE_MOVE_NEEDED",
"message": "처리 중 오류가 발생했습니다",
"data": {
"url": "FAKE_URL",
"type": "PX_RESPONSE",
"encoding": "UTF-8",
"payloads": [],
"pxResponse": {
"cardCode": null,
"paymentKey": null,
"amount": 0,
"orderId": "",
"paymentWindowType": "DEFAULT",
"paymentScheme": "STANDARD",
"resultStatus": "FAIL",
"windowTarget": "iframe",
"successUrl": "http://localhost:5173//payment-success?orderName=businessplan&email=&zip=123456&phone=&amount=661000&trial=business&lang=kr&selectedPayment=toss&customerKey=customer_3",
"failUrl": "http://localhost:5173//payment-fail",
"originUrl": "http://localhost:5173",
"error": {
"code": "2003",
"message": "처리 중 오류가 발생했습니다"
},
"redirectUrl": "http://localhost:5173/payment-fail?code=2003&message=%EC%B2%98%EB%A6%AC%20%EC%A4%91%20%EC%98%A4%EB%A5%98%EA%B0%80%20%EB%B0%9C%EC%83%9D%ED%96%88%EC%8A%B5%EB%8B%88%EB%8B%A4&orderId="
},
"extraData": null
}
}
@김차장 we got same error
ok, let me see
do you have any key value, something like "GTID", "TID" ...
@Giwon 메일주소 하나 알려주세요
💡 정보 제출
민감 정보를 안전하게 제출해주세요
@henilkevadiya
Tosspay Billing is configured to work only with hyper_toss. It is not possible to use a different clientKey. The clientKey you used belongs to bill_hyperhdxq.
@김차장 are you talking about customer key ?
입니다
이메일 입니다
@Giwon @김차장 I will talk about this. Is this the key (bill_hyperhdxq) from my side to set for a direct pop-up ?
Need to discuss with @김차장
Flow for payment
위의 에러는 다른 상점아이디 bill_hyperhdxq 를 사용해서 발생했구요
hyper_toss 를 사용하면 해결될거에요
@김차장 okay
잘 되시나요?
이메일 받았습니다
전달했습니다
빌링키를 성공적으로 받으면 이런 응답을 받게되는데요
이중에서 billingKey 값은 DB 에저장해야하고 이후 결제시 billingKey 와 함께 결제금액을 전달하면 됩니다
@henilkevadiya Please check this point also
@henilkevadiya please check
@김차장 You sent an email to @Giwon and a sample .html file that showed a successful pop-up. I implemented the same setup, except for using our own client key — but with our client key, it shows an error
Please share error detail @henilkevadiya
{
"code": "ERROR_WITH_MERT_PAGE_MOVE_NEEDED",
"message": "처리 중 오류가 발생했습니다",
"data": {
"url": "FAKE_URL",
"type": "PX_RESPONSE",
"encoding": "UTF-8",
"payloads": [],
"pxResponse": {
"cardCode": null,
"paymentKey": null,
"amount": 0,
"orderId": "",
"paymentWindowType": "DEFAULT",
"paymentScheme": "STANDARD",
"resultStatus": "FAIL",
"windowTarget": "iframe",
"successUrl": "http://localhost:8080/success.html",
"failUrl": "http://localhost:5173//payment-fail",
"originUrl": "http://localhost:5173",
"error": {
"code": "2003",
"message": "처리 중 오류가 발생했습니다"
},
"redirectUrl": "http://localhost:5173/payment-fail?code=2003&message=%EC%B2%98%EB%A6%AC%20%EC%A4%91%20%EC%98%A4%EB%A5%98%EA%B0%80%20%EB%B0%9C%EC%83%9D%ED%96%88%EC%8A%B5%EB%8B%88%EB%8B%A4&orderId="
},
"extraData": null
}
}
@김차장 same error
What customerKey did you use?
@henilkevadiya Please tell me the customerKey you used
same i used based on example
@김차장 asdf1234
1. You need to use a connectable successUrl.
2. The clientKey is used to launch the UI, and if you authenticate in the UI, the authKey and customerKey are redirected to the successUrl.
3. You need to request the authKey and customerKey received from the frontend to the backend.
@김차장 main problem is I can't able to launch UI while lunch AI i got above error that I share
@김차장 on same code I change client key from ours to test and it's lunch UI successfully
@김차장 I confirmed that Problem is not SuccessURL I just changed client key from ours to test I got below UI
and on our clientKey I got below UI and on logs I found that error
{
"code": "ERROR_WITH_MERT_PAGE_MOVE_NEEDED",
"message": "처리 중 오류가 발생했습니다",
"data": {
"url": "FAKE_URL",
"type": "PX_RESPONSE",
"encoding": "UTF-8",
"payloads": [],
"pxResponse": {
"cardCode": null,
"paymentKey": null,
"amount": 0,
"orderId": "",
"paymentWindowType": "DEFAULT",
"paymentScheme": "STANDARD",
"resultStatus": "FAIL",
"windowTarget": "iframe",
"successUrl": "http://localhost:5173/payment-success?orderName=defaultplan&email=&zip=123456&phone=&amount=500&trial=&lang=kr&selectedPayment=toss&customerKey=customer_3",
"failUrl": "http://localhost:5173/payment-fail",
"originUrl": "http://localhost:5173",
"error": {
"code": "2003",
"message": "처리 중 오류가 발생했습니다"
},
"redirectUrl": "http://localhost:5173/payment-fail?code=2003&message=%EC%B2%98%EB%A6%AC%20%EC%A4%91%20%EC%98%A4%EB%A5%98%EA%B0%80%20%EB%B0%9C%EC%83%9D%ED%96%88%EC%8A%B5%EB%8B%88%EB%8B%A4&orderId="
},
"extraData": null
}
}
Is the error page after the QR page??
@김차장 error page we got directly if we use our client key then we can't able to see QR code it show direct error
Let's check them one by one from the beginning
Please show me the code that sets the clientKey
The clientKey of hyper_toss is test_ck_Z61JOxRQVE2n9dDEQRz2rW0X9bAq. Is it used correctly?
@김차장 we copied client key from here
const tossPayments = window.TossPayments(import.meta.env.VITE_APP_TOSS_SECRET_KEY);
below is our client key
test_ck24xLea5zVAopWDNJdZbx8QAMYNwW
@김차장 below is my code to launch UI
tossPayments.requestBillingAuth("카드", {
customerKey: `customer${user_id}
,
successUrl: http://localhost:5173/payment-success`,
failUrl: "http://localhost:5173/payment-fail",
flowMode: 'DIRECT',
easyPay: 'TOSSPAY',
});
here my customer key is customer_3in here put the "hyper_toss"
Toss Pay billing only works in hyper_toss
For other general card inputs, it is correct to use bill_hyperhdxq
but here I change but it shows same error
Please upload the clientKey you confirmed here.
@김차장 for hyper_toss it show client key like this
Try using the clientKey of hyper_toss
And let me know the result
for both it show same client key
The client key is not updated on the screen?
no
use
test_ck_Z61JOxRQVE2n9dDEQRz2rW0X9bAq
@김차장 this key : test_ck_Z61JOxRQVE2n9dDEQRz2rW0X9bAq
we got pop up
we got pop up
good
@김차장 so why our client key can't work ?
The exact clientKey of hyper_toss is test_ck_Z61JOxRQVE2n9dDEQRz2rW0X9bAq
It is not updated on your screen.
okay that's why we got error
This information is correct.
After entering hyper_toss, if you click anywhere on the screen, nothing changes?
@김차장 no
@김차장 I just noticed that the client key changes when we select something from the search and then refresh the page. Otherwise, it doesn't change
When the page changes, is the test_ck_Z61JOxRQVE2n9dDEQRz2rW0X9bAq value checked? The apiKey also needs to be checked.
The apiKey ends like this
80zJwlEW
@김차장 I will talk about refresh the page not change page
@김차장 it's depends on what store id based on that this value show but after refresh the page immidate it can't change the value
In that case, I would like you to receive the mid key value through @Giwon.
You only need to check the clientKey and apiKey once.
@Giwon 오늘 지원은 여기까지 해야할거같습니다
네네 늦은시간 너무 감사합니다
키값은 개발자에게 별도 전달주셔야할거같아요
이매일로 보내주신 내용 말씀이실까요
전달했습니다
가끔 페이지 오류로인해 키값 갱신이 안되는 경우가 있는데 지금 이렇게 될줄은 몰랐네요
개발자가 토스페이 인증이 가능한가요?
QR 페이지 진행을 하려면 토스앱 회원이어야해요
제가 직접 태스트를 합니다
개발자가 요청합니다
아..네 이해했습니다
그럼.. ㅎㅎ 내일 뵙겠습니다
네 감사합니다!!
@henilkevadiya I'm going to leave after work hours. Please contact me for any issues that won't be available tomorrow.
Hello ,
@김차장 If we use the client key to generate a billing key, do we need to use the same store's secret key (named 'hyper_toss') to generate the billing key ?
yes, you should use same store's secretley.
okay
@냥과장
{ "code": "NOT_FOUND", "message": "존재하지 않는 정보 입니다." } this error means authkey expire right ?
{ "code": "NOT_FOUND", "message": "존재하지 않는 정보 입니다." } this error means authkey expire right ?
could you share the authkey you sent?
@냥과장 authkey : bln_W2ZBP7G20YA
{
code: 'INVALID_BILL_KEY_REQUEST',
message: '빌링키 인증이 완료되지 않았거나 유효하지 않은 빌링 거래 건입니다.'
}
@냥과장 and what does this error means ?
bln_W2ZBP7G20YA was already used 14:50:26 today.
you requested same request twice.
INVALID_BILL_KEY_REQUEST means you do something wrong.
please share the payload when you get this error
❤️ 기술문의 경험이 어떠셨나요?!
간단히 코멘트 남겨주세요! 제품 발전에 큰 힘이 됩니다.