Merchant guides/Raw card data/Stripe
Raw card data · Stripe · Enablement guide
Enable raw card data on your Stripe account
Stripe blocks raw PAN and CVV sent over its API until raw card data APIs are switched on for your account. This guide covers when that gate affects payments processed through Yuno, what to prepare, and the exact request to send Stripe Support — template included.
Who submits
You, the Stripe account ownerStripe handles owner requests fastest
Where
Stripe support form“Enabling access to raw card data APIs”
What to ask for
Raw card data APIs (Raw PAN gate)In both test and live environments
01Background
Why Stripe rejects the payment
When card payments run through Yuno to Stripe, Stripe may reject the request with an error like this:
Stripe API response
“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… To enable testing raw card data APIs, see https://support.stripe.com/questions/enabling-access-to-raw-card-data-apis”
Stripe blocks raw PAN/CVV usage by default. It stays blocked until Stripe explicitly enables raw card data APIs — sometimes called the Raw PAN gate — on your Stripe account.
Yuno is PCI DSS compliant and handles raw card data securely on your behalf: card details are collected and vaulted inside Yuno’s PCI-scoped environment, and only then forwarded to Stripe. The restriction is purely an account-level setting on Stripe’s side — it has to be lifted by Stripe for your specific account.
02When you need this
The two signals that the gate applies to you
Signal 1 · Failing payments
Card payments via Yuno + Stripe fail with the “Sending credit card numbers directly to the Stripe API is generally unsafe” error — in test or in production.
Signal 2 · Yuno sends the card data
You are not sending card data to Stripe yourself. Yuno does it for you as a PCI-compliant gateway — for example using the Yuno vault, with vaulted tokens mapped to Stripe payment methods.
If both are true, no change on your side or Yuno’s side will fix the declines — the enablement has to happen on your Stripe account.
03Prepare
What to have ready before opening the ticket
- Your Stripe account ID — the
acct_...identifier of the account that needs the gate lifted. - A one-line description of the setup — you process card payments via Yuno, a PCI DSS–compliant orchestration platform, and Yuno sends raw PAN/CVV to Stripe on your behalf.
- Yuno’s security reference — security.y.uno, Stripe can verify Yuno’s PCI DSS posture there.
04Submit
Open the request with Stripe
-
Open Stripe’s official form for this topic
support.stripe.com/questions/enabling-access-to-raw-card-data-apis — “Enabling access to raw card data APIs”.
-
Provide your account and the context
- Your Stripe account ID (
acct_...) - That payments are processed via Yuno, a PCI DSS–compliant orchestration platform
- That Yuno sends raw PAN/CVV to Stripe on your behalf, and payments are failing due to the raw card data restriction
- Yuno’s security page: security.y.uno
- Your Stripe account ID (
-
Ask Stripe specifically to enable the gate
Request that raw card data APIs / the Raw PAN gate be enabled for your account in both test and live environments, so Yuno can send card data directly to Stripe’s Payment Intents / Charges APIs.
05Template
Copy-paste ticket for Stripe Support
Adapt the placeholders and send it via the Stripe dashboard or email.
SubjectRequest to enable raw card data APIs (Raw PAN) for our Stripe account integrated with Yuno
Hello Stripe Support team,
We would like to request access to raw card data APIs (Raw PAN) for our Stripe account:
Account ID: acct_XXXXXXXXXXXX
We process card payments via Yuno, a PCI DSS–compliant payment orchestration platform. Yuno acts as our PCI gateway and sends card data directly to Stripe on our behalf in order to create Payment Intents / Charges.
Currently, our attempts to process card payments via Yuno are failing with the following error in Stripe: “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… To enable testing raw card data APIs, see https://support.stripe.com/questions/enabling-access-to-raw-card-data-apis.”
We understand that this is due to the raw card data restriction on our Stripe account. Since Yuno is PCI DSS compliant and handles the card data securely on our behalf, we kindly request that you:
- Enable access to raw card data APIs (Raw PAN gate) for our Stripe account, in both test and live environments.
- Confirm once this has been enabled, so that we can resume our integration tests and move to production.
For your reference, Yuno’s security and compliance details are available at: https://security.y.uno/
If you need any additional information or documentation from us or from Yuno’s team (e.g. AoC), please let us know and we’ll be happy to provide it.
Best regards,
[Merchant name]
[Company]
[Email / Phone]
06After you submit
What happens next
Stripe usually handles these requests fastest when the ticket comes directly from the account owner, mentions Yuno, and includes the security page above. Stripe occasionally asks for Yuno’s PCI Attestation of Compliance — your Yuno account team can be copied on the thread and attach it.
How to recognize that it’s done
Once Stripe enables raw card data, new payments via Yuno + Stripe go through without the “Sending credit card numbers directly to the Stripe API is generally unsafe” error. The pattern is consistent: merchant opens the ticket, Stripe enables Raw PAN, payments start working.
07References
Useful links
- Stripe · OfficialEnable access to raw card data APIs
- Yuno · Securitysecurity.y.uno — PCI and compliance information