Payment Process Requeriments

[redhot]

Hello,
I'm looking for payment processor for SAAS with recurring payments. I found the mention about the checkbox in order page, and I have a question if this realization needs to be exactly the same as described?

Important: Do not link a card on file to a customer without the customer's express permission. For example, you can include a checkbox in your purchase flow (unchecked by default) that the customer can check to specify that they wish to save their card information for future purchases. Linking cards on file without obtaining customer permission may result in your application being disabled without notice.

From customer experience point of view, it's not very well to show any checkboxes. Can I use the same implementation as popular services with Square or instead of the checkbox, show message bellow button "By submitting this form you agree to save your card for future purchases"? Also, can you give please, examples how your clients use Square with recurring payment?

[redhot]

Hello,
I'm looking for payment processor for SAAS with recurring payments. I find out mention about the checkbox in order page, and I have a question if this realization needs to be exactly the same as described?

Important: Do not link a card on file to a customer without the customer's express permission. For example, you can include a checkbox in your purchase flow (unchecked by default) that the customer can check to specify that they wish to save their card information for future purchases. Linking cards on file without obtaining customer permission may result in your application being disabled without notice.

From customer experience point of view, it's not very well to show any checkboxes. I reviewed many popular services, how they implemented payment processes and included examples with screenshots below. Can I use the same implementation as popular services with Square or instead of the checkbox, show message bellow button "By submitting this form you agree to save your card for future purchases"? Also, can you please, give some examples how your clients use Square with recurring payment?

MediumMindMeisterSlack

[Helen]

@redhot There isn't a way to change the Card on File requirement. Your customers must opt-in. If their information is saved without a physical opt-in action, as stated, it can result in your application being deactivated.

Regarding your second questions I'm happy to give you an overview of how to utilize Card on File for recurring payments. To get started:

1. You will need to embed Square's payment form in your website https://docs.connect.squareup.com/payments/sqpaymentform/sqpaymentform-setup.
2. When your customer submits their payment information, as long as the information is valid, you will receive a number — which you can use to create payments (card nonce).
3. Create a Customer with the CreateCustomer (https://docs.connect.squareup.com/api/connect/v2#endpoint-createcustomer) endpoint.
4. Next you'll create a CustomerCard with the card nonce using the CreateCustomerCard (https://docs.connect.squareup.com/api/connect/v2#endpoint-createcustomercard) endpoint.
5. Once you finish, you can charge the customer at a future date using this CustomerCard number.

Please hote: Automatic recurring payments are not supported at this time.