#sayak_api

1 messages · Page 1 of 1 (latest)

boreal lotusBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always 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/1379716542404497458

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

minor creek
#

Also has stripe deprecated passing raw card details in paymentIntents API?

vale jewel
#

Hi! Apologies for the delay! Looking into your query!

#

Express and Custom connected accounts don't have their own API keys. A platform needs to use their own key and pass a Stripe-account header (https://docs.stripe.com/connect/authentication) for requests being created on behalf of the connected account.

vale jewel
minor creek
#

i have enabled raw card support for platform account and when im passing transfer_data as "destination" my payments are going through
but when passing "direct" i get this error : "Sending credit card numbers directly to the Stripe API is generally unsafe. We suggest you use test tokens that map to the test card you are using, see https://stripe.com/docs/testing. To enable testing raw card data APIs, see https://support.stripe.com/questions/enabling-access-to-raw-card-data-apis."

Also i am passing connect account id in the headers

#

For Platform account id (acct_1JQd1YBijkbtUqNS) we have enabled raw card processing by giving our PCI certificates. So, we are able to create payments using raw card directly. Even using raw card data to create destination charge to a connected account (acct_1RQUkaB7KCg1IWRp) is working.
But when we create direct charges to a connected account (acct_1RQUkaB7KCg1IWRp) using this platform account’s (acct_1JQd1YBijkbtUqNS) API key, it is throwing this error: “”Sending credit card numbers directly to the Stripe API is generally unsafe. We suggest you use test tokens that map to the test card you are using, see https://stripe.com/docs/testing. To enable testing raw card data APIs, see https://support.stripe.com/questions/enabling-access-to-raw-card-data-apis.”
Your doc for enabling raw card data says that we just need to enable raw card data processing for Platform account only and not for connected accounts individually. Please advise how to proceed here

Test card numbers

Use test cards to validate your Stripe integration without moving real money. Test a variety of international scenarios, including successful and declined payments, card errors, disputes, and bank authentication. You can also test non-card payment methods and redirects.

vale jewel
minor creek
#

how to enable raw card support for connect accounts?

#

I also see that you are creating a direct charge for a custom account. This is not a recommended fund flow.

what is the recommended flow here? and what are we doing different?

vale jewel
boreal lotusBOT
#

We wish we could help, but you need to talk to Stripe support

We can only help on Discord if all of the following are true:

  • 🧑‍💻 You must be a developer
  • 🛠️ Your question must be about building a Stripe integration
  • ⚙️ Your question must be technical/developer focused
  • ⏱️ You must be available to respond in realtime
  • 👥 You must be comfortable receiving help in public (this is a public server)

If any of those aren't true please contact Stripe support.

If all of those are true we may have misunderstood your question; please provide more details below.

Note that using an inappropriate button or submitting inappropriate information is a violation of our rules. You will be removed from this server if you repeatedly create invalid threads.

minor creek
#

Also we reached out to stripe saying please enable raw cards for both connect and platform accounts - they say its done
Also for new connect accounts how does this enabling happen? Do we need to ask the support team everytime to enable the raw cards?

#

We have already reached out to Stripe N number of times to enable this. Can you please go back and check if its enabled in the Connect account or not? If not we can reach out to the support team - that makes sense

boreal lotusBOT
elder moss
#

hi! I'm taking over this thread.

#

we don't recommend passing raw card numbers with the API. but if your business is PCI compliant, it should be possible.

#

you need to reach out to Stripe support to get access to that feature (we can't help with this on Discord).

#

make sure to include relevant failed request ID (req_xxx) in your message to support, and clairfy that this is for a connect use case.

minor creek
#

we are PCI Compliant Level 3

#

is that enough for raw cards to be enabled?

#

also if we tokenize the card and pass the id in payment_method in the paymentIntent flow it works
but is this allowed in production? Tokenizing the card?

elder moss
#

we are PCI Compliant Level 3 is that enough for raw cards to be enabled?
no idea, that's a question for Stripe support.

#

but is this allowed in production? Tokenizing the card?
can you share a concrete example of what you are doing? like a request ID?
but if something works in test mode, it should also work in live mode;

minor creek
#

req_lCz7dlUtJkn32A

#

this is the requestId

elder moss
#

yep, that request should also work in live mode. but note that here on Discord we know nothing about PCI compliance, so I can't comment on that.