Salida (al emisor)
Unique identifier of a give session (enrolment session , Life Cycle Management session and other operation), used to link inbound and outbound requests of the same session together
Unique identifier used to identify the issuer
The unique identifier of the funding card.This value is generated and managed by the issuer.This value can be updated in case of funding PAN replacement by the issuer.
Unique identifier of the virtual card
Wallet Provider identifier, defined by Thales:
| walletProviderId | Description |
|---|---|
| APPLE_PAY | Apple Pay Wallet |
| ANDROID_PAY | Google Pay Wallet |
| SPAYHCE | Samsung Pay Wallet |
Card unique identifier defined by the Wallet Provider or the primary TSP.For ApplePay, it corresponds to the FPANID. For Fidesmo/Digiseq, it corresponds to the card identifier provided by the primary TSP.
Wallet virtual card identifier.For ApplePay, it corresponds to the auxiliary DPANID.
Primary wallet virtual card identifier.For ApplePay, it corresponds to the primary DPANID.
Unique token storage identifier
It is a boolean information that inform if the virtual card is a primary virtual card or if it is an auxiliary virtual card. Always set to false in this API.
This corresponds to the action performed on the token
Here are the possible values:
- ACTIVATE: When the virtual card is activated after provisioning.
- SUSPEND: When the active virtual card is suspended.
- RESUME: When the suspended virtual card is re-activated.
- DELETE: When the virtual card deleted.
- UPDATE: When the funding PAN value is updated (ex: card renewal).
- ERASE: When a virtual card is erased following a GDPR action.
Token information in JSON. This field is conditional to the TSP and provided only during enrolment.
This value is encrypted using the PKCS#7 encryption scheme defined in RFC 2315/5652 using following encryption parameters:
- The content encryption algorithm used is AES256/CBC/PKCS7Padding using a randomly generated AES key.
- The key encryption algorithm is either RSAES-PKCS1-v1_5 (RSA/NONE/PKCS1Padding) or RSA/NONE/OAEPWithSHA256AndMGF1Padding (with MGF1 using SHA-256), using the certificate provided during onboarding. The key encryption algorithm is defined during onboarding and is by default (if ommitted) the RSA/NONE/PKCS1Padding for legacy purpose. It is recommended to configure RSA/NONE/OAEPWithSHA256AndMGF1Padding (with MGF1 using SHA-256) for new issuers.
- The encryption result is then encoded using base64.
- The public key length in the certificate can be 2048-bit or 4096-bit.
Once deciphered, the cardInfo contains the following information:
| JSON field parameter name | description | MOC | Length |
|---|---|---|---|
| pan | The token PAN. | M | Up to 19 |
| exp | The expiry date in the format MMYY. | M | 4 |
Identifier of the key used to encrypt tokenInfo.Provided by Issuer to Thales during onboarding.
Error code provided in case of operation failure initiated by the issuer
| reason code | description |
|---|---|
| 113 | Unknown issuer |
| 115 | Unknown product |
| 119 | Unknown Token |
| 221 | The device was not reachable after retries |
| 322 | Time to live of the operation expired |
| 911 | Operation failed |
| 921 | Unexpected error |
This list is not exhaustive. Error codes not listed shall be considered as a generic error.
The source actor that initiated the state change
Successful
Sin contenido
Bad Request, Invalid request URI or header, or unsupported nonstandard parameter
Internal Server Error
Sin contenido
Unique identifier of a give session (enrolment session , Life Cycle Management session and other operation), used to link inbound and outbound requests of the same session together
Unique identifier used to identify the issuer
Successful
Bad Request, Invalid request URI or header, or unsupported nonstandard parameter
Internal Server Error
Sin contenido
Unique identifier of a give session (enrolment session , Life Cycle Management session and other operation), used to link inbound and outbound requests of the same session together
Unique identifier used to identify the issuer
The card information in JSON, encrypted using the PKCS#7 encryption scheme defined in RFC 2315/5652 using following encryption parameters:
- The content encryption algorithm used is AES256/CBC/PKCS7Padding using a randomly generated AES key.
- The key encryption algorithm is either RSAES-PKCS1-v1_5 (RSA/NONE/PKCS1Padding) or RSA/NONE/OAEPWithSHA256AndMGF1Padding (with MGF1 using SHA-256), using the certificate provided during onboarding. The key encryption algorithm is defined during onboarding and is by default (if ommitted) the RSA/NONE/PKCS1Padding for legacy purpose. It is recommended to configure RSA/NONE/OAEPWithSHA256AndMGF1Padding (with MGF1 using SHA-256) for new issuers.
- The encryption result is then encoded using base64.
- The public key length in the certificate can be 2048-bit or 4096-bit.
Once deciphered, the cardInfo contains the following information:
| JSON field parameter name | description | MOC | Length |
|---|---|---|---|
| fpan | The funding pan to digitize | M | Up to 19 |
| exp | The expiry date in the format MMYY | O | 4 |
| cvv | Depending of the OEM and scheme, this value is provided or not | O | 3 or 4 |
Examples:
Example 1
{
"fpan":"1234567891234567",
"exp":"1218",
}
Example 2
{
"fpan":"1234567891234567",
"exp":"1218",
"cvv":"765"
}
The encrypted data contains the original token information used with primary TSP (Token for Token provisioning). This is only applicable for HCE Wallet. The original token information in JSON is encrypted using the PKCS#7 encryption. See encryption of cipheredCardInfo for more details. Once deciphered the tokenInfo contains the following information:
| JSON field parameter name | description | MOC | Length |
|---|---|---|---|
| originalTokenRequestorId | Token Requestor Identifier of the original token provided and allocated by Scheme TSP | O | Up to 11 |
| originalTokenId | The original token identifier as defined by the Scheme TSP.For VISA (VTS) it corresponds to vProvisionedTokenIDMandatory if originalToken is not provided. | C | Up to 64 |
| originalToken | The original token used to request the digitization with primary TSPMandatory if originalTokenId is not provided. | C | Up to 19 |
Identifier of the key used to encrypt cipheredCardInfo.Provided by Issuer to Thales during onboarding.
The unique identifier of the funding card.This value is generated and managed by the issuer.This value can be updated in case of funding PAN replacement by the issuer.
Wallet Provider identifier, defined by Thales:
| walletProviderId | Description |
|---|---|
| APPLE_PAY | Apple Pay Wallet |
| ANDROID_PAY | Google Pay Wallet |
| SPAYHCE | Samsung Pay Wallet |
Card unique identifier defined by the Wallet Provider or the primary TSP.For ApplePay, it corresponds to the FPANID. For Fidesmo/Digiseq, it corresponds to the card identifier provided by the primary TSP.
requestCoBadgeDigitization response payload
The unique identifier of the funding card.This value is generated and managed by the issuer.This value can be updated in case of funding PAN replacement by the issuer.
The payment account reference value to associate with the token.The usage of this optional field depends on the solution and the personalization profile.
The domestic card information in JSON, encrypted using the PKCS#7 encryption scheme defined in RFC 2315/5652 using following encryption parameters:
- The content encryption algorithm used is AES256/CBC/PKCS7Padding using a randomly generated AES key.
- The key encryption algorithm is either RSAES-PKCS1-v1_5 (RSA/NONE/PKCS1Padding) or RSA/NONE/OAEPWithSHA256AndMGF1Padding (with MGF1 using SHA-256), using the certificate provided during onboarding. The key encryption algorithm is defined during onboarding and is by default (if ommitted) the RSA/NONE/PKCS1Padding for legacy purpose. It is recommended to configure RSA/NONE/OAEPWithSHA256AndMGF1Padding (with MGF1 using SHA-256) for new issuers.
- The encryption result is then encoded using base64.
- The public key length in the certificate can be 2048-bit or 4096-bit.
Once deciphered, the payload shall contain the following information:
| JSON field parameter name | description | MOC | Length |
|---|---|---|---|
| fpan | The domestic funding pan to digitize | M | Up to 19 |
| exp | The expiry date in the format MMYY | O | 4 |
Examples:
{
"fpan":"1234567891234567",
"exp":"1228",
}
Identifier of the key used to encrypt cipheredDomesticCard.Provided by Thales to Issuer during onboarding.
Bad Request, Invalid request URI or header, or unsupported nonstandard parameter
Internal Server Error
Última actualización
¿Te fue útil?