How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

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.![Card production status flow](/images/diagrams/card-production-status-flow.png)

Wise card-kiosk-collection API is one of 48 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.2.0.

Requests are made against 2 base URLs: https://api.wise.com, https://api.wise-sandbox.com.

2 operations 1 paths 1 schemas 1 GET1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
Base URL
https://api.wise.com/v2
Authentication
HTTP Bearer, HTTP Bearer, HTTP Bearer, HTTP Basic
Resource Areas
1

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.

card-kiosk-collection 2

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…

PUT
/v3/spend/profiles/{profileId}/cards/{cardToken}/production
Produce a card
cardKioskCollectionProduce 3 params body → 200422429
GET
/v3/spend/profiles/{profileId}/cards/{cardToken}/production
Retrieve card production status
cardKioskCollectionProductionGet 3 params → 200429

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.

ProductionStatus
object
Represents the production status of a card at a kiosk machine.
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

wise-card-kiosk-collection-api-openapi.yml Raw ↑

Other APIs Wise publishes across the network.

Wise 3ds API
Wise activity API
Wise address API
Wise balance API
Wise balance-statement API
Wise bank-account-details API
Wise batch-group API
Wise bulk-settlement API
Wise card API
Wise card-order API
Wise card-sensitive-details API
Wise card-transaction API
Where this information came from

This is an independent, third-party profile of Wise card-kiosk-collection API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.