#Toss payment billing with Bubble.io

21 messages · Page 1 of 1 (latest)

candid lintel
#

Hi everyone, I'm working on the Toss payment billing in Bubble.io, as a plugin.
In the card registration process, I thought it is supposed to go to 1 of 2 pages: success or fail.
But even when it's failed, it still go to the success page, is that the way this process work? or I did something wrong?

golden falconBOT
#
⏳ 잠시만 기다려주세요! 곧 답변드리겠습니다

오류 문의일 경우 아래 정보를 미리 전달해주시면, 빠른 답변에 도움이 됩니다.

- 주문번호(orderId) : - 문의 내용 :

(img를 함께 첨부해주시면 도움이됩니다)

tawdry tendon
#

what was your costomerkey when you got this error?

#

success page means issuing auth code was success.

#

Then you request billlingkey using auth code.

#

the error came from requesting billing key

#

so payment window -> successURL-> request billlkey- > error

candid lintel
#

what is the customer key supported to be?
I'm sorry, I'm still new to these things, I took the user unique id for the customer key.

tawdry tendon
#

You shoud read this guide first.

#

this page explains what is customerkey and why you send it.

candid lintel
#

I'm creating the subcription payment (automatically pay once every month), so what should I do now? Putting this workflow in the backend and make it run once every month?

tawdry tendon
#

yes, payment by billkey is for actual payment. so you can running a workflow and call it whenever you want

candid lintel
#

I'm sorry, what you said make me confused. As I know, Billing is specialized for recurring automatic payments (regular payment), not actual payment.

tawdry tendon
#

yes you are right.

golden falconBOT
#
❤️ 기술문의 경험이 어떠셨나요?!

간단히 코멘트 남겨주세요! 제품 발전에 큰 힘이 됩니다.

candid lintel
#

Hi, me again. Thank you for your support. I'm still struggling with the Toss billing.
Could you tell me where I need to get the customerKey from? Because from what I read, the customer Key shouldn't be the user ID.

candid lintel
tawdry tendon
#

customerkey is the value that was requesting from your side when you asked the billingkey.

#

it is generate by your side not ours.

#

but you should enter same value in billingwindow and calling api.