#k3davis-Intents
lapis halo
sure, i grant that was confusing. trying to be concise in the first message 🙂
our nonprofit is integrating stripe for the first time for credit card donations. our donation pages are not authenticated, meaning we don't know with certainty who the donor is at time of a charge being created, which may be a one time charge or a single charge with an intent to recur later.
it seems that to use paymentelement for PCI compliance we must create a paymentintent to accomplish that initial charge. but the "customer" making that payment may already be a customer in stripe, so we don't want to create a new one. we want to link that payment to an existing customer after the fact, at least if they will have off-session charges later.
in my head (probably wrong) this could be a "guest" paymentintent which later can be added as a setupintent to a known customer
near plaza
have you considered using Checkout for your donations?
lapis halo
not really, as that would be outside the flow of our web site, and I believe would require "items" of fixed amounts?
i'm not trying to solve the subscription problem, but rather prevent every donation made (since it's made "anonymously" as far as our database is concerned) from creating a new customer in stripe
near plaza
and I believe would require "items" of fixed amounts?
not really you could useprice_datato create a custom amount
lapis halo
alright, i guess i'm unclear about how that solves the problem
near plaza
sorry I'm not following your concerns then, let me try to rephrase
you are trying to create a way for your customers to do donations, you want them to be able to do anonymous donations or doing a recurring donation (in that case the customer is no longer anonymous) right?
lapis halo
maybe the issue would be clearer if i removed the subscription concern.
the donor goes to the donation page which uses stripe.js to collect card or bank data, enters an amount etc., and submits their gift. This creates a paymentintent that is linked to an unknown customer. I presume this is a "guest" since we didn't explicitly create a customer as part of this flow.
We reconcile that gift in our system and know that paymentintent/payment method is associated with customer 1234. But we can't move that payment in stripe to that customer, even if they exist as a customer in stripe already.
Every gift given from a stripe.js form seems to create a new customer, even if the email and everything is the same
near plaza
how are you using the Payment Intents? Are you using Payment Element?
lapis halo
that is what I understood we have to do to use the client side collection and avoid pci scope. we are not doing anything yet, i'm just trying to understand it
(technically we are using payment intents already, but in a purely backend integration. i'm trying to move the payment handling to the front end)
near plaza
In that case I would suggest you take a look at this doc https://stripe.com/docs/payments/payment-intents
it would explain how to create the Payment Intent on the server and use the client_secret on the front-end with PaymentElement
another very good resource is https://stripe.com/docs/payments/accept-a-payment?ui=elements
lapis halo
alright, i've read these but they don't seem to address the issue. but i will take another look and learn how to ask my question better. 😉 thanks for your efforts.