Merchant guides

Merchant guides/Raw card data/Adyen

Raw card data · Adyen · Enablement guide

Enable raw card data on your Adyen account

In the Adyen live environment, sending raw PAN and CVV over the API requires a specific role on your Web Service (WS) user — and Adyen validates your PCI certification before granting it. This guide covers when that applies to payments processed through Yuno, what to prepare, and the exact request to raise with Adyen — template included.

Who submits

You, the Adyen account ownerVia the dashboard or your Adyen TAM

Where

Adyen support ticketca-test.adyen.com / ca-live.adyen.com

What to ask for

Raw card data / PCI payments roleOn the WS user Yuno uses, plus PCI validation

01Background

Why Adyen gates raw PAN

When you connect Adyen card acquiring via Yuno, Adyen may require that your account be explicitly allowed to send raw card data (PAN + CVV) over the API. Three things determine whether that permission is in place:

If the role is missing

Without this role — and without Adyen having validated PCI compliance for the account — card payments sent as raw card data may fail or simply not be allowed in live, even when everything works in test.

02When it’s required

Three scenarios that need the request

Scenario 1

Yuno sends PAN/CVV to Adyen via API

You use Yuno checkout, SDK, or server-to-server, and Yuno decrypts and forwards PAN/CVV to Adyen — e.g. via Yuno Vault or a one-time token mapped to paymentMethod.number / paymentMethod.cvc.

Scenario 2

API-only card integration

You process cards API-only, with no Adyen-hosted components, and want to send raw card data instead of (or alongside) Adyen’s own encrypted components. Adyen requires the WS-user role plus validation of your PCI certification.

Scenario 3

Production go-live

Sandbox tests can pass while live processing stays blocked — the PCI / raw card role has to be enabled on the live Adyen account and its WS user as well.

Not needed for APMs

Alternative payment methods such as PIX and Boleto are always supported via API-only integration and do not require raw card data permissions.

03Prepare

What to have ready before opening the ticket

04Submit

Raise the request with Adyen

The exact UI may vary slightly, but the flow is typically:

  1. Log in to the Adyen dashboard

    Test: ca-test.adyen.com · Live: ca-live.adyen.com — pick the environment that needs the role.

  2. Go to Support / Contact — or your Adyen TAM

    Open a support ticket from the dashboard, or reach out to your Adyen account manager directly.

  3. Use a clear subject

    “Request to enable raw card data / PCI payments role for API-only card integration with Yuno”

  4. Provide the details and the explicit request

    • Company account and merchant account codes
    • The WS user / API credential used by Yuno
    • Your PCI DSS status — attach your AoC if you are PCI certified
    • The integration description with Yuno (see the template below)
    • An explicit ask to enable the raw card data / PCI payments role for that WS user, and to confirm it covers API-only card integrations where Yuno sends PAN/CVV to Adyen

  5. Share the reference links if needed

    Adyen raw card data docs and security.y.uno.

05Template

Copy-paste ticket for Adyen Support

Adapt the placeholders and send it to Adyen Support or your Adyen TAM.

Support ticket · Ready to adapt

SubjectRequest to enable raw card data / PCI payments role for API-only card integration with Yuno

Hello Adyen Support team,

We would like to request enablement of raw card data processing for our API-only card integration, using the Adyen Web Service (WS) user that Yuno will use.

Our details are:

  • Company account: <Your Company Account>
  • Merchant account(s): <Your Merchant Account Code(s)>
  • WS user / API credential: <WS user or API credential name used by Yuno>

Integration with Yuno

We process card payments via Yuno, a PCI DSS Level 1 payment orchestration platform. Yuno:

  • Receives cardholder data in a PCI-scoped environment
  • Tokenizes and securely stores the card data
  • Sends raw PAN/CVV to Adyen using our Adyen credentials, as part of an API-only card integration (paymentMethod.number, paymentMethod.cvc, paymentMethod.expiryMonth, paymentMethod.expiryYear)

Our own PCI DSS status is: <“We are PCI DSS compliant and can share our AoC on request” or “We rely on Yuno’s PCI DSS Level 1 environment and do not store PAN/CVV in our systems.”>

For reference:

  • Adyen raw card data documentation: https://docs.adyen.com/payment-methods/cards/raw-card-data
  • Yuno security and PCI compliance: https://security.y.uno

Request

We kindly ask Adyen to:

  1. Enable the raw card data / PCI payments role for the above WS user / API credential, so that we can send raw PAN/CVV via API.
  2. Confirm that this configuration is valid for API-only card integrations where Yuno sends the card details directly to Adyen on our behalf.

If any additional documentation is required (e.g. a PCI AoC from us or from Yuno), please let us know and we will provide it.

Thank you very much for your support.

Best regards,
<Name>
<Company>
<Email / Phone>

06After you submit

What happens next

Adyen reviews the request and validates the PCI certification path you declared — your own AoC, or reliance on Yuno’s PCI DSS Level 1 environment — before assigning the role to the WS user. If Adyen asks for Yuno’s PCI Attestation of Compliance, your Yuno account team can join the thread and provide it.

Verify on the right environment

The role is granted per environment. If you are going live, confirm it is enabled on the live company account and WS user — passing sandbox tests does not carry over.

07References

Useful links

Also in this series Enable raw card data on your Stripe account →