Jaywan issuer guide
Follow Jaywan v1.2 provisioning, OTP delivery, and lifecycle events.
Lume Token connects your programme to the Jaywan TSP. In Notification mode, it processes scheme requests and returns responses while your systems receive the common notification envelope. This guide targets the Jaywan issuer interface v1.2.
Scheme operations
For this version, activation methods are supplied in provisioning. A separate Get User Validation Methods request is not part of the v1.2 flow described here. The scheme's health check is not a card-provisioning event or an issuer notification example.
Provisioning examples
The synthetic notifications below include selected eligible native fields and illustrative Lume enrichment. paymentologyPublicCardToken, velocityRules, and decisioningReason are Lume additions. Protected card data and encrypted token data are omitted, so these examples are not raw Jaywan requests. issuerCardRefId is the TSP funding-card reference; virtualCardId identifies the tokenized virtual card.
Provisioning (TAR)
This example selects a yellow path and SMS verification. The wallet-supplied scoringInformation.levelOfTrust is an input, distinct from the issuer outcome. A processor status of 0000 indicates successful processing; it does not distinguish green, yellow, orange or red provisioning outcomes.
{
"MESSAGE_TYPE": {
"Message_Type": "TAR",
"Message_Desc": "Tokenization Authorization Request",
"Version": "2"
},
"SUMMARY": {
"Api_Call_Unique_Identifier": "evt-jaywan-tar-001",
"Token": 123456789,
"Token_Status": 1000,
"PID": 123,
"Client_Id": 123456,
"Source": "Jaywan TSP",
"Network": "JAYWAN",
"Date_Time": "2026-10-02 10:15:30.000",
"Processor_Decision_Code": "0000",
"Wallet": "Apple",
"Device": "PHONE",
"OTP": null,
"Message_Reason": "provisioning",
"Token_Requestor_Id": "08600010003"
},
"ADDITIONAL_MESSAGE_DATA": {
"walletProviderId": "APPLE_PAY",
"issuerCardRefId": "funding-jaywan-example-001",
"virtualCardId": "virtual-card-example-001",
"paymentologyPublicCardToken": 123456789,
"tncStatus": true,
"tncAcceptedDate": "2026-10-02T10:14:30.000Z",
"cardCaptureInformation": {
"captureMethod": "MANUAL"
},
"scoringInformation": {
"levelOfTrust": "yellow"
},
"velocityRules": {
"blocked": false
},
"decisioningReason": {
"decision": "REQUIRE_ADDITIONAL_AUTHENTICATION",
"ruleName": "Manual wallet step-up",
"activationMethods": [
{
"id": "sms-example-001",
"type": "cell_phone",
"value": "*******4567"
}
]
}
}
}The selected native provisioning response fields for this example are:
{
"issuerCardRefId": "funding-jaywan-example-001",
"statusCode": "0000",
"levelOfTrust": "yellow",
"idvMethodList": [
{
"id": "sms-example-001",
"type": "cell_phone",
"value": "*******4567"
}
]
}Lume returns the scheme response. Your Notification endpoint records TAR and acknowledges it. The id in idvMethodList connects the offered method to the subsequent OTP request. These selected fields are not a complete provisioning response.
Send Selected Validation Method (OTP)
Deliver the code through the channel associated with otpMethodId, using your cardholder contact record. It matches the id offered in the provisioning response. The example shows the issuer-facing OTP value after protected transport handling, not an encrypted scheme field to forward to the cardholder.
{
"MESSAGE_TYPE": {
"Message_Type": "OTP",
"Message_Desc": "Tokenization Activation Code Request",
"Version": "2"
},
"SUMMARY": {
"Api_Call_Unique_Identifier": "evt-jaywan-otp-002",
"Token": 123456789,
"Token_Status": 1000,
"PID": 123,
"Client_Id": 123456,
"Source": "Jaywan TSP",
"Network": "JAYWAN",
"Date_Time": "2026-10-02 10:16:30.000",
"Processor_Decision_Code": null,
"Wallet": "Apple",
"Device": "PHONE",
"OTP": "123321",
"Message_Reason": "sendSelectedValidationMethod",
"Token_Requestor_Id": "08600010003"
},
"ADDITIONAL_MESSAGE_DATA": {
"walletProviderId": "APPLE_PAY",
"issuerCardRefId": "funding-jaywan-example-001",
"virtualCardId": "virtual-card-example-001",
"paymentologyPublicCardToken": 123456789,
"otpValue": "123321",
"expirationDate": "2026-10-02T10:22:30.000Z",
"otpMethodId": "sms-example-001"
}
}LCM Event Notification (TNR)
After successful activation, update the token identified by virtualCardId. action is the native lifecycle action. isPrimary distinguishes a primary token from an auxiliary token in a co-badged programme; this example is primary.
{
"MESSAGE_TYPE": {
"Message_Type": "TNR",
"Message_Desc": "Tokenization Notification Request",
"Version": "2"
},
"SUMMARY": {
"Api_Call_Unique_Identifier": "evt-jaywan-tnr-003",
"Token": 123456789,
"Token_Status": 1000,
"PID": 123,
"Client_Id": 123456,
"Source": "Jaywan TSP",
"Network": "JAYWAN",
"Date_Time": "2026-10-02 10:17:30.000",
"Processor_Decision_Code": null,
"Wallet": "Apple",
"Device": "PHONE",
"OTP": null,
"Message_Reason": "Token Notification: ACTIVATED",
"Token_Requestor_Id": "08600010003"
},
"ADDITIONAL_MESSAGE_DATA": {
"walletProviderId": "APPLE_PAY",
"issuerCardRefId": "funding-jaywan-example-001",
"virtualCardId": "virtual-card-example-001",
"paymentologyPublicCardToken": 123456789,
"isPrimary": true,
"action": "ACTIVATE",
"tokenType": "SE"
}
}The same native method reports SUSPEND, RESUME, DELETE, and UPDATE. UPDATE concerns funding-card updates and must not be treated as another activation. Keep primary and auxiliary token records separate even when they share the funding card.
What to test
Verify provisioning decisions, the methods returned in provisioning, method-ID continuity through OTP delivery, and activation completion. For co-badged programmes, test primary and auxiliary lifecycle events independently.
Updated 20 days ago