#grizzly - raw card details
zealous ridge
Thank you!
low yoke
You need to make sure you read about the PCI implications of this:
https://stripe.com/docs/security/guide#validating-pci-compliance > API Direct tab
You will need to provide documentation showing your PCI compliance in order to be able to do this
Is there any Stripe implementation that I can use?
What do you mean, you said you did not want to use Elements, so what are you looking for in this sense?
zealous ridge
Yes, definitely. The company is working on getting PCI compliant. But for valid reasons, they do not want to use Checkout (currently implemented), nor Elements.
We would like to process a single-payment, without redirecting to Stripe Checkout page, and without any embedded UI component as an iframe.
We would like to use our own frontend, which collects raw card details, and process a payment directly through API.
We were recommended to use Direct Charges, but I don't think it's possible to do so without working with Checkout or Elements.
Could you be able to recommend what exact feature we should use? i.e. PaymentIntents?
low yoke
OK, and what exactly do you need help with to achieve that?
zealous ridge
We are not sure what the exact Stripe implementation we should integrate.
For example, I tried to use PaymentIntents which allowed me to process a payment directly through the Stripe API. Is there any other way you would recommend?
low yoke
We recommend using Elements, generally, but can support direct API
If you've got Payment Intents working like this, it sounds like you have what you need
You said you have such payment working already right? Do you have specific concerns or questions about that?
zealous ridge
We don't really have a concern about PaymentIntents. However, we are trying to find alternatives. We were told to integrate Direct Charges, however, the latter requires Stripe Checkout or Elements to accept the payment as a UI, which we do not want.
That's the only concern, that's why we are trying to find what alternatives we have other than PaymentIntents (which definitely works).
low yoke
Ok, let's take a step back
Do you mean "direct charges" as in charges to a standard connected account using Connect? Since you were describe api-direct charges without elements I was in that mindset, but there may be two different meanings of "direct" here.
Are you using Connect?
zealous ridge
https://stripe.com/docs/connect/direct-charges
This is the exact direct charges that I'm talking about
So I assume it's using Connect
zealous ridge
The payment here is processed using Stripe Checkout OR an embedded UI component as an iframe
What we want is to create our own User Interface, and process a payment through Stripe. Is this possible (without PaymentIntents)?
OR, can we use ApplicationFeeAmount attribute in PaymentIntents, instead of going to Connect - Direct Charges?
low yoke
You can set an application fee only for connect related charges, it doesn't make sense outside that context
Yes I understand you want to collect card details yourself, but I thought you described already doing that part
zealous ridge
So is it possible to use PaymentIntents with Connect-Direct Charges?
I'm basically using the raw card details to create a PaymentMethod object, and then using that PaymentMethod to process a PaymentIntent using a PaymentIntentService. If I add the attribute 'ApplicationFeeAmount', would that flow work?
low yoke
Yes, those payment methods created with card details directly sent to the API can be used with those direct charges