#NLPeezy
1 messages · Page 1 of 1 (latest)
- You can but you must be PCI compliant. This is quite difficult to achieve, so we provide Elements.
- Where do you see that message? With Elements that shouldn't show up
First of all, great username name and thanks for assisting. Here is the very basic script in PHP just as a POC.
Oh if you pass setup_future_usage, then that message appears
We have to show that in that case
and we have to if we want to save payment info for use, right?
Because setup future usage sets up the card to be charged in the future
Yeah if you are going to set it up to be charged in the future while the customer is offline you need that param
And we have to provide that notice to the customer
Understood thanks. Back to question 1, we have a pretty robust PCI compliant program already, so we are considering using our own HTML form. Does that mean we would directly hit these API's? https://stripe.com/docs/api/charges/object
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Yeah PaymentIntents not Charges
If you want the newer, recommended flow
But Payment Element is recommended. If the issue is just styling, you can use the appearance api: https://stripe.com/docs/payments/customize-payment-element#appearance-api
Thank you much! I'll go back and talk to the team. I really appreciate the assist, have a great weekend.
No problem. Same to you!