Wise card-kiosk-collection API
These APIs are designed to allow you to print and encrypt your card directly from a kiosk machine. The card information will be sent to our card manufacturer to configure and print the card on-site on a kiosk machine.The card printing process will automatically begin once the request is received by our card manufacturer.During the printing process, you will be notified via webhook about any [card production status change](/guides/developer/webhooks/event-types#cards-card-production-status-change).Before using these APIs, make sure to read the guide on [kiosk collection](/guides/product/issue-cards/card-kiosk-collection#card-kiosk-collection).{% admonition type="warning" %}Please reach out to your Implementation Manager for more information on these APIs.{% /admonition %}**Testing**: In the sandbox environment, use the [card production simulation API](/api-reference/simulation/simulationcardproduction) to test your integration with various production statuses and error scenarios.Production status flow {% .title-2 .m-t-5 %}These statuses represent the lifecycle of a card production:- `READY` - Card is ready for production. The [produce card endpoint](/api-reference/card-kiosk-collection/cardkioskcollectionproduce) can be called.- `IN_PROGRESS` - Card is being produced at the kiosk machine (chip encryption and printing in progress).- `PRODUCED` - Card has been successfully produced and collected from the kiosk. This is a final state.- `PRODUCTION_ERROR` - Card production failed. Check the errorCode to identify the issue, resolve it, then retry using the [produce card endpoint](/api-reference/card-kiosk-collection/cardkioskcollectionproduce).A card with production status `PRODUCED` will trigger an asynchronous call to update the associated card order to `PRODUCED` status.
Wise card-kiosk-collection 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-kiosk-collection. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an AsyncAPI specification.
This API exposes 2 operations across 1 path, and defines 1 schema. 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-kiosk-collection 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 2
Across 1 path, the API surfaces 2 operations — 1 GET, 1 PUT. Each is listed below with its method, path, parameters, and response codes.
These APIs are designed to allow you to print and encrypt your card directly from a kiosk machine. The card information will be sent to our card manufacturer to configure and prin…
Schemas 1
The contract defines 1 schema that model the data the API accepts and returns. The most detailed is ProductionStatus (5 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Wise 12
Other APIs Wise publishes across the network.