#christian_ece-link

1 messages ¡ Page 1 of 1 (latest)

spare fernBOT
dusty roverBOT
#

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

spare fernBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1260707257004327063

📝 Have more to share? Add details, code, screenshots, videos, etc. below.

plain pine
#

christian_ece-link

#

@placid depot My understanding is that Link doesn't really support "on session reuse" so it doesn't make sense to try and achieve this.

placid depot
#

yeah we were thinking that too. Do you mind explaining the difference between on_session and null? I understand off_session as you are declaring that the current payment can be used in the future but what benefit do I have in declaring that a payment will come again in the future via the same way?

plain pine
#
  • null => You don't save the PaymentMethod at all and won't reuse it for future payments, you'd just collect a new PaymentMethod for the next one
  • on_session => You save the PaymentMethod and it's attached to the Customer. In the future, when the Customer comes back to pay again you show them a UI with their saved PaymentMethod(s) object for them to pick from instead of having to re-enter for example card details. (what Amazon does for example when you pay). This is not compatible with Link.
  • off_session => You save the PaymentMethod and it's attached to the Customer. In the future, you can charge that Customer's PaymentMethod however you like, for example if you are a hotel you can charge for incidentals when they check out, or if it was a "subscription" with recurring payments. off_session implies on_session so you can still show a UI to let them pay with that saved card