Wise card-sensitive-details API
Wise is a PCI DSS compliant provider and stores all card data securely. The scope for PCI compliance depends on your use case and will impact how you integrate. For all sensitive card details endpoints, follow the [detailed guide](/guides/product/issue-cards/sensitive-card-details).**Key capabilities:**- Access sensitive card data (PAN, CVV, PIN) via encrypted JWE payloads**Related operations:**- For card management (list, status, permissions), see the [Cards API](/api-reference/card)- For ordering new cards, see the [Card Orders API](/api-reference/card-order)- For transaction history, see the [Card Transaction API](/api-reference/card-transaction)
Wise card-sensitive-details API is one of 47 APIs that Wise publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.
Tagged areas include card-sensitive-details. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an AsyncAPI specification.
This API exposes 3 operations across 3 paths. It is described by OpenAPI 3.1.0.
Requests are made against 2 base URLs: https://api.wise.com, https://api.wise-sandbox.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 4
Wise card-sensitive-details API declares
4 security schemes
for authenticating requests.
It accepts HTTP bearer tokens (JWT) (UserToken).
It accepts HTTP bearer tokens (JWT) (PersonalToken).
It accepts HTTP bearer tokens (JWT) (ClientCredentialsToken).
It accepts HTTP basic authentication (BasicAuth).
UserToken— User Access Token for making API calls on behalf of a Wise user. Can be obtained via two OAuth 2.0 flows: - registrationcode grant: For partners creating users…PersonalToken— Personal API Token for individual personal or small business users. Generated from Wise.com Settings Connect and manage apps API tokens. Has limited API access…ClientCredentialsToken— Application-level token for partner operations that don't require a specific user context, such as bulk settlement and card spend controls. Obtained via POST /…BasicAuth— Basic Authentication using your Client ID and Client Secret as the username and password. Client credentials are provided by Wise when your partnership begins.…
Paths & Operations 3
Across 3 paths, the API surfaces 3 operations — 1 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.
Wise is a PCI DSS compliant provider and stores all card data securely. The scope for PCI compliance depends on your use case and will impact how you integrate. For all sensitive…
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Wise 12
Other APIs Wise publishes across the network.