#zzking

1 messages · Page 1 of 1 (latest)

full oysterBOT
royal wasp
#

Hi 👋

If you use the Payment Element as part of saving the customer payment method information, the mandate is collected. The Payment Element displays mandate text as part of the rendered interface so that when the user clicks the button to save their payment method it serves as the acknowledgement of the mandate.

peak kindle
#

Thanks.. We are building our own UI, on which there will be a checkbox which asks permission to "store the payment method for future usage". Would that be enough as "mandate" ?

royal wasp
#

No, in that case you will want to review mandate language carefully

peak kindle
#

Sorry, what do you mean exactly in that case you will want to review mandate language carefully ?

royal wasp
#

A mandate offers legal protection for the merchant and acknowledgement for charges on the part of the customer

peak kindle
#

WHen you suggest to use Payment Element , I assume the "mandate" is also just some text ?

royal wasp
#

Yes

peak kindle
#

sorry .. when I say the text is "store the payment method for future usage", it's just an example. I'll let our legal team design the actual language. What I want to ask is : is that enough that we provide some well -designed text as "mandate" ?

royal wasp
#

By providing your card information, you allow {{merchant_name}} to charge your card for future payments in accordance with their terms.

This is what is rendered on my test account (with the merchant name filled in). Yes if you have the language present then that should cover you.

peak kindle
#

aha OK. Just to confirm: as long as we have good legal language to show on OUR UI (like the example you just showed), it should be good enough to count as "Mandate" to charge our customer's client's card details later. Am I correct ?

I just want to make sure the "mandate" is not something that we need to set as part of API request that we send to Stripe , or some extra logic (coding wise). The "mandate" is just some well-defined text that our customer's clients should see and agree upon if they wish.

royal wasp
peak kindle
#

aha OK. So I need to :

  1. Create the SetupIntent and let customer fill in the credit card details
  2. Show on the UI the "mandate", which will be a well-defined legal text like the example that you shown.
  3. Once customer agrees the "mandate" (e.g: by ticking the checkbox) and clicks "save". I need to confirm the SetupIntent with "mandate_data".
  4. "Payment Element" is not mandatory, as we will use our own UI.

AM I correct ?

royal wasp
#

Correct

peak kindle
#

great, thank you !