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
TSH sends Card information as a JSON.
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 |
|---|---|---|---|
| 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 |
| additionalCardInfos | Optional JSON Open format, in order to add additional card info - project dependent | O | Up to 8177 |
Examples:
Example 1
{
"fpan":"1234567891234567",
"exp":"1218",
}
Example 2
{
"fpan":"1234567891234567",
"exp":"1218",
“cvv":"765”
}
Example 3
{
"fpan":"1234567891234567",
"exp":"1218",
“cvv":"765”,
"additionalCardInfos": {
"archiveReference": “90217095220928”
}
}
Example 4
{
"fpan":"1234567891234567",
"exp":"1218",
"additionalCardInfos": {
"pin": “06123456FFFFFFFF”
}
}
Note:
- This parameter is optional, If it not provided, the Issuer must rely on the issuerCardRefId to find
the funding card to digitize.cipheredCardInfo and issuerCardRefId are exclusive
- pin is sent inside additionalCardInfos only in case of UPI scheme. It is generally sent for Debit cards.
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 manage by the issuer.
This value can be updated in case of funding PAN replacement by the issuer.
The following is valid for enrolment of domestic card (not valid for VISA & Mastercard): This parameter is optional, If it not provided, the Issuer must rely on the cipheredCardInfo to get the funding PAN and find the funding card to digitize.
Wallet Provider identifier, defined by Thales.
When TSH acts as OEM Pay broker:
| walletProviderId | Description |
|---|---|
| APPLE_PAY | Apple Pay Wallet |
| SPAYHCE | Samsung Pay Wallet |
| ANDROID_PAY | Google Pay Wallet |
When TSH acts as ITSP:
| walletProviderId | Description |
|---|---|
| WALLET | Generic NFC/QR Code Wallet provider |
| ECOM | Generic Merchant Wallet Provider ID managing CoF token |
NOTE: It is possible to assign a specific "walletProviderId" for a given TRID. This configuration can be achieved during the project on-boarding phase only.
Please check the "Wallet Provider ID Mapping" page in the "API Reference" section.
Method used by the user or the issuer to capture card information to digitize.
Description:
- CAMERA: when card information is captured by the on-device camera
- MANUAL: when the consumer enters the card information manually, through the device keyboard
- BANK_APP: when the card information is exchanged between the banking App and the Issuer App
- ON-FILE: when the card information is retrieved by a merchant who has stored the card information
- READER_MODE: when the card information is retrieved through a NFC interaction between the device and the physical card (applicable to VISA, MASTERCARD, AMEX, DISCOVER and some domestic schemes)
- TOKEN: when the card information is retrieved through a device-based token. This is applicable only to VISA and MASTERCARD schemes
- CHIP_DIP: card information is captured by inserting (dip) the card into a terminal (applicable to VISA & MASTERCARD)
- WEB_BROWSER: card information (PAN) is captured through a web browser (applicable only to MasterCard & AMEX schemes)
- UNKNOWN: the origin of the card information is unknown
checkCardEligibility response payload
The unique identifier of the funding card.
This value is generated and manage by the issuer.
This value can be updated in case of funding PAN replacement by the issuer.
Unique identifier of the card product associated to the card to digitize.
It is used by TSH or the TSP scheme to identify the proper card arts and card profile metadata to send to the wallet.
In case of an international scheme, card arts and card metadata are configured by the Issuer with the scheme directly, TSH does not host any data.
Conditional field:
- For international schemes: the field is required or not according to the configuration the Issuer has choosen with the scheme. TSH will forward it to the TSP if the field is available.
- For domestic schemes: required in case TSH is not able to determine the card product profile based on the (sub)BIN
Bad Request, Invalid request URI or header, or unsupported nonstandard parameter
Internal Server Error
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
TSH sends Card information as a JSON.
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 |
|---|---|---|---|
| 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 |
| additionalCardInfos | Optional JSON Open format, in order to add additional card info - project dependent | O | Up to 8177 |
| originalToken | The device-based token used to request the digitization | O | Up to 19 |
| originalTokenReferenceID | The unique reference of the original Token | O | Up to 32 |
| originalTokenAssuranceLevel | The assurance level of the orginal Token - RFU | O | 2 |
Examples:
Example 1
{
"fpan":"1234567891234567",
"exp":"1218",
}
Example 2
{
"fpan":"1234567891234567",
"exp":"1218",
“cvv":"765”
}
Example 3
{
"fpan":"1234567891234567",
"exp":"1218",
“cvv":"765”,
"additionalCardInfos": {
"archiveReference": “90217095220928”
}
}
Example 4
{
"fpan":"1234567891234567",
"exp":"1218",
"additionalCardInfos": {
"pin": “06123456FFFFFFFF”
}
}
Example 5: Token for Token digitization
{
"fpan":"1234567891234567",
"exp":"1218",
“cvv":"765”,
"originalToken":"4532111111111112",
"originalTokenReferenceID":"DNITHE381835220225004085",
"originalTokenAssuranceLevel":""
}
Note:
- This parameter is optional, If it not provided, the Issuer must rely on the issuerCardRefId to find the funding card to digitize. cipheredCardInfo and issuerCardRefId are exclusive.
- pin is sent inside additionalCardInfos only in case of UPI scheme. It is generally sent for Debit cards.
- originalToken,originalTokenReferenceID and originalTokenAssuranceLevel are provided ONLY by VISA in case of a Token for Token digitization flow.
The unique identifier of the funding card.
This value is generated and manage by the issuer.
This value can be updated in case of funding PAN replacement by the issuer.
The following is valid for enrolment of domestic card (not valid for VISA & Mastercard): This parameter is optional, If it not provided, the Issuer must rely on the cipheredCardInfo to get the funding PAN and find the funding card to digitize.
Wallet Provider identifier, defined by Thales.
When TSH acts as OEM Pay broker:
| walletProviderId | Description |
|---|---|
| APPLE_PAY | Apple Pay Wallet |
| SPAYHCE | Samsung Pay Wallet |
| ANDROID_PAY | Google Pay Wallet |
When TSH acts as ITSP:
| walletProviderId | Description |
|---|---|
| WALLET | Generic NFC/QR Code Wallet provider |
| ECOM | Generic Merchant Wallet Provider ID managing CoF token |
NOTE: It is possible to assign a specific "walletProviderId" for a given TRID. This configuration can be achieved during the project on-boarding phase only.
Please check the "Wallet Provider ID Mapping" page in the "API Reference" section.
Wallet card unique identifier Conditional: If provided by Wallet provider.
An additional authentication value provided by end user or third party application through the Wallet Provider It can be for example the CVV value entered by end user
In case of CVV : The base64 represent the encrypted buffer of the JSON :
{
"cvv":"123"
}
Encryption is done using PKCS#7 in RFC2315/5652 as for the cipheredCardInfo using Issuer Certificate Conditional: it depends of the Wallet Provider, some are managing an authenticationValue and others not.
Identifier of the key used to encrypt cipheredCardInfo and authenticationValue.
Provided by Issuer to Thales during onboarding.
T&C acceptance status by end user. Value is "true" if T&C have been accepted, "false" otherwise.
Date of T&C acceptance by end user in ISO 8601 format YYYY-MM-DDThh:mm:ssTZD
true if the TSP has verify the CVV2 on behalf of the issuer false if TSP failed to verify the CVV2 not provided if TSP doesn't manage to verify the CVV2
The type of token the TSP has created or for which the request is sent. It applies to VISA, MasterCard and UPI. Following values are supported:
- SE (token for a secure element)
- HCE (token for Host Card Emulated device)
- COF (token for a card on file)
- ECOM (token for ecommerce)
- QRC (token for QRCode)
requestCardDigitization response payload
The unique identifier of the funding card.
This value is generated and manage by the issuer.
This value can be updated in case of funding PAN replacement by the issuer.
Unique identifier of the card product associated to the card to digitize.
It is used by TSH or the TSP scheme to identify the proper card arts and card profile metadata to send to the wallet.
In case of international schemes, card arts and card metadata are configured by the Issuer with the scheme directly, TSH does not host any data.
Conditional field, if provided, TSH will forward it to the TSP.
Issuer Level of trust of the customer and Card Information Value can be: • 'green' : good level of trust, no ID&V requested • 'yellow' : warning, ID&V is required • 'red' : reject the digitization Conditional: not provided in case of error. Mandatory in case of success.
The amount quota, if the transaction amount exceeds it, the terminal shall prompt the cardholder to provide the Online PIN. This field is only returned for UPI scheme. And it is not applicable for other schemes.
Bad Request, Invalid request URI or header, or unsupported nonstandard parameter
Internal Server Error
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
Wallet Provider identifier, defined by Thales.
When TSH acts as OEM Pay broker:
| walletProviderId | Description |
|---|---|
| APPLE_PAY | Apple Pay Wallet |
| SPAYHCE | Samsung Pay Wallet |
| ANDROID_PAY | Google Pay Wallet |
When TSH acts as ITSP:
| walletProviderId | Description |
|---|---|
| WALLET | Generic NFC/QR Code Wallet provider |
| ECOM | Generic Merchant Wallet Provider ID managing CoF token |
NOTE: It is possible to assign a specific "walletProviderId" for a given TRID. This configuration can be achieved during the project on-boarding phase only.
Please check the "Wallet Provider ID Mapping" page in the "API Reference" section.
The unique identifier of the funding card.
This value is generated and manage by the issuer.
This value can be updated in case of funding PAN replacement by the issuer.
Unique identifier of the virtual card
The purpose of requestIDnVLisr:
- ENROLMENT: the requestIDnVList is sent in the context of a card enrollment to create a virtual card
- DEVICE_BINDING: the requestIDnVList is sent in the context of a device binding
- CARDHOLDER_STEPUP: the requestIDnVList is sent in the context of a cardHolderVerification
Reference of the device binding process/link to the Virtual Card, reference is unique per token. It helps to identify each device link to a given Virtual Card. Note this field corresponds to:
- the deviceIndex for VTS
- the authCorrelationId for MDES
The Issuer can:
- approve request without IDVList --> no stepup is required.
- approve with stepup. Then IDVList is returned.
Bad Request, Invalid request URI or header, or unsupported nonstandard parameter
Internal Server Error
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
Reference of the device binding process/link to the Virtual Card, reference is unique per token. It helps to identify each device link to a given Virtual Card. Note this field corresponds to:
- the deviceIndex for VTS
- the authCorrelationId for MDES
Unique identifier of the virtual card
Wallet Provider identifier, defined by Thales.
When TSH acts as OEM Pay broker:
| walletProviderId | Description |
|---|---|
| APPLE_PAY | Apple Pay Wallet |
| SPAYHCE | Samsung Pay Wallet |
| ANDROID_PAY | Google Pay Wallet |
When TSH acts as ITSP:
| walletProviderId | Description |
|---|---|
| WALLET | Generic NFC/QR Code Wallet provider |
| ECOM | Generic Merchant Wallet Provider ID managing CoF token |
NOTE: It is possible to assign a specific "walletProviderId" for a given TRID. This configuration can be achieved during the project on-boarding phase only.
Please check the "Wallet Provider ID Mapping" page in the "API Reference" section.
The unique identifier of the funding card.
This value is generated and manage by the issuer.
This value can be updated in case of funding PAN replacement by the issuer.
The following is valid for enrolment of domestic card (not valid for VISA & Mastercard): This parameter is optional, If it not provided, the Issuer must rely on the cipheredCardInfo to get the funding PAN and find the funding card to digitize.
requestDeviceBinding response payload
Issuer Level of trust of the device binding Value can be: • 'green' : good level of trust, no ID&V requested • 'yellow' : warning, ID&V is required • 'red' : reject the digitization Conditional: not provided in case of error. Mandatory in case of success.
Bad Request, Invalid request URI or header, or unsupported nonstandard parameter
Internal Server Error
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 manage by the issuer.
This value can be updated in case of funding PAN replacement by the issuer.
Unique identifier of the virtual card
Wallet card unique identifier Conditional: If provided by Wallet provider.
Wallet virtual card identifier For ApplePay, it corresponds to the DPANID and is always provided if defined.
Wallet Provider identifier, defined by Thales.
When TSH acts as OEM Pay broker:
| walletProviderId | Description |
|---|---|
| APPLE_PAY | Apple Pay Wallet |
| SPAYHCE | Samsung Pay Wallet |
| ANDROID_PAY | Google Pay Wallet |
When TSH acts as ITSP:
| walletProviderId | Description |
|---|---|
| WALLET | Generic NFC/QR Code Wallet provider |
| ECOM | Generic Merchant Wallet Provider ID managing CoF token |
NOTE: It is possible to assign a specific "walletProviderId" for a given TRID. This configuration can be achieved during the project on-boarding phase only.
Please check the "Wallet Provider ID Mapping" page in the "API Reference" section.
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
This corresponds to the action performed on the token
Here is the possible value:
- ACTIVATE : Token First Activation
- SUSPEND : Token suspended via lifecycle operation
- RESUME : Token resumed via lifecycle operation
- DELETE : Token deleted on the TSP
- DELETE_FROM_APP : Token deleted on the wallet application (MDES only)
- UPDATE : When the funding PAN value is updated (ex: card renewal)
- RENEW : When a token is renewed (ex: if the token expire, the TSP renew the token and re-provision it automaticaly)
- ERASE : Token erased following a GDPR action
- DEVICE_BOUND : Token bound to a device (VISA & MASTERCARD only)
- DEVICE_UNBOUND : Token unbound from a device (VISA only)
- CARDHOLDER_STEPUP_OTP, CARDHOLDER_STEPUP_ISSUER_APP, CARDHOLDER_STEPUP_CALL_CENTER: in case of cardholder authentication flow (VISA only)
- CARDHOLDER_STEPUP_APPROVED: in case of cardholder authentication flow performed via 3D Secure (VISA only)
Provided only in case of DEVICE_BOUND / DEVICE_UNBOUND action. Note that this field corresponds to the deviceIndex for VTS and to the bindId for MDES. For MDES Device Binding, in case of error, this field will include the authCorrelationId to help with trouble-shooting.
Additional information about the token of the virtual card This field is conditional to the TSP and provided only during enrolment.
Only supported in case of token managed by VTS or MDES The tokenInfo is the json (cf http://www.json.org/ ) representation of the Token.
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. It is not provided for UPI scheme. | C | 4 |
| originalToken | The device-based token used to request the digitization | O | Up to 19 |
| originalTokenReferenceID | The unique reference of the original Token | O | Up to 32 |
| originalTokenAssuranceLevel | The assurance level of the orginal Token - RFU | O | 2 |
NOTE
originalToken,originalTokenReferenceID and originalTokenAssuranceLevel are provided ONLY by VISA in case of a Token for Token digitization flow.
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
| error code | description |
|---|---|
| 221 | The device was not reachable after retries |
| 322 | Time to live of the operation expired |
| 432 | Current token state does not allow this operation |
| 520 | Stepup cardholder authentication failed |
| 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 initiate the state change.
Description: -WALLET -TSP -ISSUER
The type of token the TSP has created or for which the request is sent. It applies to VISA, MasterCard and UPI. Following values are supported:
- SE (token for a secure element)
- HCE (token for Host Card Emulated device)
- COF (token for a card on file)
- ECOM (token for ecommerce)
- QRC (token for QRCode)
The token assurance level indicates the level of assurance of the token. This is given by the ID&V method that has been used to authenticate the consumer on the specific token for example when the token is created (during the digitization flow) or, in case of a COF token, when a binding flow is executed.
Following values are supported:
- 00 (ID&V not performed)
- 10 (Card Issuer Account Verification)
- 11 (Card Issuer Interactive Verification - 1 Factor)
- 12 (Card Issuer Interactive Verification - 2 Factor)
- 13 (Card Issuer Oriented Non-Interactive Cardholder Authentication)
- 14 (Card Issuer Asserted Authentication)
NOTE: applies only to VISA
Successful (no response body)
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
Wallet Provider identifier, defined by Thales.
When TSH acts as OEM Pay broker:
| walletProviderId | Description |
|---|---|
| APPLE_PAY | Apple Pay Wallet |
| SPAYHCE | Samsung Pay Wallet |
| ANDROID_PAY | Google Pay Wallet |
When TSH acts as ITSP:
| walletProviderId | Description |
|---|---|
| WALLET | Generic NFC/QR Code Wallet provider |
| ECOM | Generic Merchant Wallet Provider ID managing CoF token |
NOTE: It is possible to assign a specific "walletProviderId" for a given TRID. This configuration can be achieved during the project on-boarding phase only.
Please check the "Wallet Provider ID Mapping" page in the "API Reference" section.
The unique identifier of the funding card.
This value is generated and manage by the issuer.
This value can be updated in case of funding PAN replacement by the issuer.
Reference of the binding between the device and the token. Provided in case the OTP must be sent in the process of a Device Biding flow. This field is provided only when the flow is going through VTS (Note that this field corresponds to the deviceIndex).
The otp value to be send by the issuer. The value is mandatory for VTS. For MDES it won't be provided in case of In-App Verification via Push Notification
The expiration time for OTP. ex. 2015-05-18T14:40:32.000Z
CYY-MM-DDTHH:MM:SSz Value will be in GMT.
The identifier of OTP method selected by end user
This identifier is defined by the issuer and shared with TSH in response of the requestCardDigitization
It corresponds to the id field defined in the idvMethod of the requestCardDigitization.response.idvMethodList.idvMethod
Successful (no response body)
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
TSH sends Card information as a JSON.
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 |
|---|---|---|---|
| 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 |
| additionalCardInfos | Optional JSON Open format, in order to add additional card info - project dependent | O | Up to 8177 |
| originalToken | The device-based token used to request the digitization | O | Up to 19 |
| originalTokenReferenceID | The unique reference of the original Token | O | Up to 32 |
| originalTokenAssuranceLevel | The assurance level of the orginal Token - RFU | O | 2 |
Examples:
Example 1
{
"fpan":"1234567891234567",
"exp":"1218",
}
Example 2
{
"fpan":"1234567891234567",
"exp":"1218",
“cvv":"765”
}
Example 3
{
"fpan":"1234567891234567",
"exp":"1218",
“cvv":"765”,
"additionalCardInfos": {
"archiveReference": “90217095220928”
}
}
Example 4
{
"fpan":"1234567891234567",
"exp":"1218",
"additionalCardInfos": {
"pin": “06123456FFFFFFFF”
}
}
Example 5: Token for Token digitization
{
"fpan":"1234567891234567",
"exp":"1218",
“cvv":"765”,
"originalToken":"4532111111111112",
"originalTokenReferenceID":"DNITHE381835220225004085",
"originalTokenAssuranceLevel":""
}
Note:
- This parameter is optional, If it not provided, the Issuer must rely on the issuerCardRefId to find the funding card to digitize. cipheredCardInfo and issuerCardRefId are exclusive.
- pin is sent inside additionalCardInfos only in case of UPI scheme. It is generally sent for Debit cards.
- originalToken,originalTokenReferenceID and originalTokenAssuranceLevel are provided ONLY by VISA in case of a Token for Token digitization flow.
Unique identifier of the virtual card
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
Inform at which step the STIP notification has been recevied by TSH during the enrollment.
Description: -NEW_SESSION -CARD_ELIGIBILITY_IN_PROGRESS -CARD_ELEGIBILITY_DONE -CARD_DIGITIZATION_IN_PROGRESS -CARD_DIGITIZATION_DONE -SEND_OTP_IN_PROGRESS -SEND_OTP_DONE -NOTIFY_CARD_STATUS_IN_PROGRESS -NOTIFY_CARD_STATUS_DONE
Current token state.
Description: -SUSPENDED -RESUMED -DELETED -UPDATED -INACTIVE
Additional information about the token of the virtual card This field is conditional to the TSP and provided only during enrolment. Only supported in case of token managed by VTS or MDES
Identifier of the key used to encrypt tokenInfo.
Provided by Issuer to Thales during onboarding.
Wallet Provider identifier, defined by Thales.
When TSH acts as OEM Pay broker:
| walletProviderId | Description |
|---|---|
| APPLE_PAY | Apple Pay Wallet |
| SPAYHCE | Samsung Pay Wallet |
| ANDROID_PAY | Google Pay Wallet |
When TSH acts as ITSP:
| walletProviderId | Description |
|---|---|
| WALLET | Generic NFC/QR Code Wallet provider |
| ECOM | Generic Merchant Wallet Provider ID managing CoF token |
NOTE: It is possible to assign a specific "walletProviderId" for a given TRID. This configuration can be achieved during the project on-boarding phase only.
Please check the "Wallet Provider ID Mapping" page in the "API Reference" section.
Wallet card unique identifier Conditional: If provided by Wallet provider.
The source actor that initiate the state change.
Description: -WALLET -TSP -ISSUER
true if the TSP has verify the CVV2 on behalf of the issuer false if TSP failed to verify the CVV2 not provided if TSP doesn't manage to verify the CVV2
The token assurance level indicates the level of assurance of the token. This is given by the ID&V method that has been used to authenticate the consumer on the specific token for example when the token is created (during the digitization flow) or, in case of a COF token, when a binding flow is executed.
Following values are supported:
- 00 (ID&V not performed)
- 10 (Card Issuer Account Verification)
- 11 (Card Issuer Interactive Verification - 1 Factor)
- 12 (Card Issuer Interactive Verification - 2 Factor)
- 13 (Card Issuer Oriented Non-Interactive Cardholder Authentication)
- 14 (Card Issuer Asserted Authentication)
NOTE: applies only to VISA
notifyStandInProcess response payload
The unique identifier of the funding card.
This value is generated and manage by the issuer.
This value can be updated in case of funding PAN replacement by the issuer.
Bad Request, Invalid request URI or header, or unsupported nonstandard parameter
Internal Server Error
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
succesfull
Bad Request, Invalid request URI or header, or unsupported nonstandard parameter
Internal Server Error
Sin contenido
Última actualización
¿Te fue útil?