> ## Documentation Index > Fetch the complete documentation index at: https://docs.tagada.io/llms.txt > Use this file to discover all available pages before exploring further. # Raw card data capability (SDK internal) > Used by `@tagadapay/node-sdk` `paymentInstruments.createFromCard()`. Returns the public, create-only vault key the SDK uses to tokenize a card **from the merchant's server directly into Tagada's PCI vault** — the card number never reaches the Tagada API. Not meant to be called by hand. The capability is off by default and enabled per account by Tagada support. When it is not enabled the endpoint answers `403` with `Please contact support to ask for raw card data enablement`. ## OpenAPI ````yaml /openapi.json get /api/public/v1/payment-instruments/raw-card/config openapi: 3.0.3 info: title: TagadaPay API description: >- # TagadaPay API Documentation Welcome to the TagadaPay API. This REST API lets you process payments, manage subscriptions, handle customers, deploy plugins, and orchestrate checkout funnels — all programmatically. ## Authentication Authenticate every request with a Bearer token. Get your API key from the [TagadaPay Dashboard](https://app.tagada.io). ``` Authorization: Bearer your-api-key ``` All requests must be made over HTTPS with `Content-Type: application/json`. ## Rate Limits | Plan | Requests/min | Burst | |------|-------------|-------| | Standard | 100 | 150 | | Premium | 500 | 750 | Exceeding the limit returns `429 Too Many Requests`. ## Errors | Code | Meaning | |------|---------| | 400 | Bad request — invalid parameters | | 401 | Unauthorized — missing or invalid API key | | 403 | Forbidden — insufficient permissions | | 404 | Not found | | 409 | Conflict | | 429 | Rate limited | | 500 | Server error | ## Support - Email: api-support@tagada.io - Docs: [docs.tagadapay.com](https://docs.tagadapay.com) version: 1.0.0 servers: - url: https://api.tagada.io/ description: Production - url: https://api.tagada.dev/ description: Sandbox / Development security: - bearerAuth: [] tags: - name: auth description: Test your API key and verify authentication. - name: stores description: Create and manage stores within your account. - name: products description: Create products with variants, prices, and currency options. - name: customers description: Manage customer records, addresses, and payment instruments. - name: orders description: List and retrieve orders with line items, payments, and metadata. - name: payments description: Process, list, refund, void, and dispute payments. - name: subscriptions description: >- Create and manage recurring subscriptions — billing, cancellation, rebilling, and processor changes. - name: payment-flows description: Configure payment routing strategies with cascading processor fallbacks. - name: payment-instruments description: >- Manage stored payment methods — cards, bank accounts, and tokenized instruments. - name: processors description: List connected payment processors (Stripe, NMI, Checkout.com, etc.). - name: promotions description: Create and manage discount promotions with rules and conditions. - name: promotion-codes description: Generate and manage reusable promotion/coupon codes. - name: block-rules description: >- Configure fraud prevention rules to block transactions by IP, email, card BIN, country, etc. - name: webhooks description: Register webhook endpoints to receive real-time event notifications. - name: events description: Query application events, statistics, and audit logs. - name: domains description: Add, verify, and manage custom domains for your checkout and funnels. - name: funnels description: >- Create and manage checkout funnels with routing, A/B testing, and CDN deployment. - name: funnel-sessions description: Retrieve funnel session data for analytics and debugging. - name: funnel-tracking description: Track funnel step events for conversion analytics. - name: plugins description: Deploy, manage, and configure checkout plugins. - name: plugins-v2 description: >- V2 plugin system — deploy, mount, split-test, fork, promote, and manage plugin instances. - name: checkout description: >- Initialize checkout sessions and process payments through the hosted checkout. - name: 3ds description: >- 3D Secure authentication — create sessions, authenticate, and handle challenges. - name: builder description: Generate and validate builder session tokens for the visual page editor. - name: health description: API health check endpoint. - name: test description: Test and debugging utilities for the event system (sandbox only). paths: /api/public/v1/payment-instruments/raw-card/config: get: tags: - payment-instruments summary: Raw card data capability (SDK internal) description: >- Used by `@tagadapay/node-sdk` `paymentInstruments.createFromCard()`. Returns the public, create-only vault key the SDK uses to tokenize a card **from the merchant's server directly into Tagada's PCI vault** — the card number never reaches the Tagada API. Not meant to be called by hand. The capability is off by default and enabled per account by Tagada support. When it is not enabled the endpoint answers `403` with `Please contact support to ask for raw card data enablement`. operationId: get-api-public-v1-payment-instruments-raw-card-config parameters: [] responses: '200': description: Successful response content: application/json: schema: type: object properties: enabled: type: boolean enum: - true tokenization: type: object properties: provider: type: string enum: - basistheory publicApiKey: type: string description: Public, create-only vault application key tokenizeUrl: type: string description: Vault endpoint the SDK posts the card to required: - provider - publicApiKey - tokenizeUrl required: - enabled - tokenization examples: enabled: summary: Capability enabled value: enabled: true tokenization: provider: basistheory publicApiKey: key_prod_us_pub_… tokenizeUrl: https://api.basistheory.com/tokens default: $ref: '#/components/responses/error' security: - bearerAuth: [] components: responses: error: description: Error response content: application/json: schema: type: object properties: message: type: string code: type: string issues: type: array items: type: object properties: message: type: string required: - message additionalProperties: false required: - message - code additionalProperties: false securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT description: 'Enter your API key as: `Bearer your-api-key`' ````