Creates a reusable token from the payment method a previous transaction stored.
POST
/api/tokens/create-from-transaction-async
deprecated
No permission required.
This is the tokenize-after-the-fact path, for a card or check already charged. The transaction is read within `merchantId` only: one belonging to another merchant is reported as not found. The resulting token charges like any other, so supply its public reference as `TokenData.Token`. No card number or full account number crosses the wire in either direction: the request carries only identifiers, and the response carries the token handles plus masked and last-four values. A transaction that stored no reusable payment method is refused with a coded business error. `customerId` is accepted so callers can pass the customer they intend to attach the token to, but it is not stored on the token itself.
Signed in, you can send this request to your own sandbox merchant from the console and read the answer. Sign in to try it.
Example request
Every block below sends the same request. Replace {{BASE_URL}} with the address of the API you are calling and {{API_KEY}} with your own key.
The request body is a . See the Request body section below for its fields.
Parameters
| Name | In | Type | Description |
|---|---|---|---|
transactionId
required |
query | string (uuid) | The prior transaction to mint the token from. |
merchantId
required |
query | string (uuid) | The owning merchant. Must be within the caller's scope, and the transaction must belong to it. |
customerId
required |
query | string (uuid) | Optional customer the caller intends to attach the token to. Not stored on the token. |
suppressNulls
required |
query | boolean | If true, omit properties with null values. |
Request body
application/json
, required
| Field | Type | Description |
|---|
This request body has no documented fields.
Responses
200 OK
Body: CreateStandaloneTokenResponseDto
Each item has these fields.
| Field | Type | Description |
|---|---|---|
id
required |
string (uuid) | The internal vault record id of the minted token. Deprecated for external use: charge with `publicReference` instead. |
numericToken
required |
integer (int64) | Legacy numeric form of the token, retained for existing internal callers and back-compat. Not the preferred external handle: use `publicReference`. nullable |
cardFormatToken
required |
string | Legacy card-format (PAN-shaped) form of the token, retained for existing internal callers and back-compat. Not the preferred external handle: use `publicReference`. nullable |
publicReference
required |
string | The chargeable public reference of the minted token (the opaque `pt_`-prefixed handle). nullable |
maskedPaymentDetails
required |
PaymentDetailSnapshot | |
type
required |
TokenType | Defines the supported token types used in transaction-related models. Also aliased as the platform's payment-method category (`InitializeContext` imports it as `PaymentMethodCategory`), which is what the processor-profile pre-filter narrows on. one of: Card, Check, Cash, DigitalWallet, AlternativePayment |
category
required |
TokenCategory | Defines the category of a token used in transaction processing. one of: Internal, Network, Wallet |
idempotencyStatus
required |
all of StandaloneTokenCreateIdempotencyStatus | What create idempotency did to the request that produced this response. |
This response has no documented body fields.
403 Forbidden
Body: RemoteServiceErrorResponse
Each item has these fields.
| Field | Type | Description |
|---|---|---|
error
required |
RemoteServiceErrorInfo |
This response has no documented body fields.
401 Unauthorized
Body: RemoteServiceErrorResponse
Each item has these fields.
| Field | Type | Description |
|---|---|---|
error
required |
RemoteServiceErrorInfo |
This response has no documented body fields.
400 Bad Request
Body: RemoteServiceErrorResponse
Each item has these fields.
| Field | Type | Description |
|---|---|---|
error
required |
RemoteServiceErrorInfo |
This response has no documented body fields.
404 Not Found
Body: RemoteServiceErrorResponse
Each item has these fields.
| Field | Type | Description |
|---|---|---|
error
required |
RemoteServiceErrorInfo |
This response has no documented body fields.
501 Not Implemented
Body: RemoteServiceErrorResponse
Each item has these fields.
| Field | Type | Description |
|---|---|---|
error
required |
RemoteServiceErrorInfo |
This response has no documented body fields.
500 Internal Server Error
Body: RemoteServiceErrorResponse
Each item has these fields.
| Field | Type | Description |
|---|---|---|
error
required |
RemoteServiceErrorInfo |
This response has no documented body fields.
default The request failed. The body carries the standard error envelope: a machine-readable `error.code`, a human-readable `error.message`, and `error.validationErrors` when the failure was a validation rejection. See the error-code reference in this document's description for the values `error.code` can take.
Body: RemoteServiceErrorResponse
Each item has these fields.
| Field | Type | Description |
|---|---|---|
error
required |
RemoteServiceErrorInfo |
This response has no documented body fields.
429 The request was refused because a rate limit was exceeded, or because something a later retry can clear stopped it. A rate limit refusal carries an `application/problem+json` body: wait at least the interval `Retry-After` names before retrying, then back off. Limits are tuned per deployment, so read the allowance from the response headers rather than assuming a fixed ceiling. Any other refusal carries the standard error envelope as `application/json`, and its `error.code` names the cause.
Body: RemoteServiceErrorResponse
Each item has these fields.
| Field | Type | Description |
|---|---|---|
error
required |
RemoteServiceErrorInfo |
This response has no documented body fields.
Errors
A failed request returns the platform error envelope. The
error reference lists every value
error.code can carry and shows the four response shapes.