jungleworks_docs

[desert forge]

👋 Welcome to your new thread!

⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1256178050299727924

📝 Have more to share? Add details, code, screenshots, videos, etc. below.

[austere summit]

hi! just https://stripe.com/docs/payments/save-during-payment

[cinder bough]

I have gone through this documentation also, but we are sending card details in this API. So, how are we going to tell the card details?

[austere summit]

not sure I follow, can you elaborate? you mean you are PCI certified to handle card PANs?

[cinder bough]

We want an API in which we can send card details, and payment details, and it directly get paid through that API without any requirement to hit any other API. And if card details are incorrect, then it return the fail response.

[austere summit]

are you PCI certified to handle card PANs?

[cinder bough]

Yes

[austere summit]

well then https://support.stripe.com/questions/enabling-access-to-raw-card-data-apis is the process to get permission to use APIs that accept raw details.

[cinder bough]

right now our flow is like-
we are making payments through cards via stripe and it is done in 2 steps. First, we request for setup intent for the card details , and then make the request for the payment intent.
but now we want it to be done only in one step through one API for both setup intent and payment intent. how can it be achieved

[cinder bough]

Can you please elaborate a little bit

[austere summit]

I know, you already said that.

You can do it one request by creating a PaymentIntent with setup_future_usage and confirm set, see the docs linked earlier.

[austere summit]

what can I elaborate on?

[cinder bough]

Yes , I got your point here that I can set it by using setup_futue_usage, but in the API shown in the stripe's documentation, card details are not being sent. Can we put card details in this API?

[austere summit]

you can, if you have access to the feature that allows that

it's not really documented since 99% of users would never do this

[cinder bough]

okay. got it.

what will be the format and structure of card details?

[austere summit]

when you get access to the feature the team will share docs for it

[cinder bough]

and keys and values that we would have to pass for card details

okay, so first of all we have to get permissions to use APIs that accept raw details? like you mentioned above?

[austere summit]

yes

[cinder bough]

okay

but, is it possible if we do not want to go get these permissions and only want to change in the existing flow to send card details? Because, currently all of our clients are using stripe embedded form flow for making transactions.

[austere summit]

and what's wrong with the embedded form?

Like I said initially : https://docs.stripe.com/payments/save-during-payment lets you charge and save the card details at once(instead of using a SetupIntent and then a separate PaymentIntent like you described). That is what I would do.

[cinder bough]

So, in this, I can send card details also? if yes, please tell the format of sending the card details. Because fromat is not mentioned in this doc

[glossy raptor]

Hey! Taking over for my colleague. Let me catch up.

[cinder bough]

Hey!

[glossy raptor]

What you mean exacly by "sending card details"? for example you mean the card raw number ?

[cinder bough]

yes

is there any other way?

[glossy raptor]

Nope.

[glossy raptor]

The link my colleague shared is what you need actually, if your integration is PCI-DSS compliant

[cinder bough]

so , what is the format of sending card details

[glossy raptor]

First of all why you want to send raw card data ?

[cinder bough]

So, I can save card details and make payment in one go through the link you shared?

[glossy raptor]

And not using SetupIntents ? Have you had the chance to run through this guide < https://docs.stripe.com/payments/save-during-payment >?

[cinder bough]

because our client needs it. c

[glossy raptor]

If you want to charge the customer and save the payment method in one shot, then you need to follow this guide:
https://docs.stripe.com/payments/save-during-payment

[cinder bough]

Yeah, I got your point. I have gone through this doc

[glossy raptor]

First check the latest guide I shared (use payment_intent with setup_future_usage), and then teel us what is missing and why you explciitly want to send raw card details.

if there is no strong reason for that, I strongly discourage you from doing that.

[glossy raptor]

Yes please.

[cinder bough]

But, the link you shared doesn't display the card details format

[cinder bough]

I have gone through it, I couldn't find JSON object in which sample card details are sent

[austere summit]

yep, I already said "it's not really documented since 99% of users would never do this"

once you have access to the ability to do this you can ask the team to share docs with you of how it's done

[cinder bough]

It means mandatorily have to get these permissions. otherwise i can not do this

[austere summit]

yes

there's no way around that, if you want to send raw PANs, you need to engage with our support team and prove you are PCI compliant, per the support article shared earlier.