New Card Link Format with Risk Evaluation

🚀 Real-Time Risk Evaluation for Card Link!

We're thrilled to announce a powerful new enhancement to the Card Link request format — introducing STANDARD_V1_WITH_RISK! 🎉

This game-changing upgrade enables issuers to perform real-time risk evaluation during the card link request, building on the rock-solid foundation of STANDARD_V1 and adding full support for transmitting risk signals in both the request and the response. ⚡

✨ What's New

1. 🆕 New Request Format: `STANDARD_V1_WITH_RISK`

Say hello to the next evolution of the STANDARD_V1 format! This enhanced format introduces a brand-new areq field containing the AReq message — with sensitive fields carefully redacted for security.

🔒 Redacted fields (handled securely via the card section):

acctNumber
cardholderName
cardExpiryDate

The card section is flexible and powerful, supporting:

🔐 Encrypted, hashed, or plain text values (based on your configuration)
👤 Optional inclusion of cardholderName, aligned with the same rules as accountNumber

📋 Example Request

{
  "format": "STANDARD_V1_WITH_RISK",
  "card": {
    "accountNumber": "4111111111111111",
    "expiry": "2027-12",
    "cardholderName": "Christian Horner"
  },
  "device": {
    "channel": "BROWSER",
    "ip": "1.2.3.4",
    "language": "en-EN"
  },
  "transaction": {
    "version": "2.2.0",
    "id": "fc028fa7-1cec-48df-a871-ee9f512418e7",
    "dsTransactionId": "98315a91-e0b6-4fe0-8842-9ed82ea8ef0b",
    "category": "PAYMENT",
    "merchantId": "mer-12345",
    "merchantName": "Amazon",
    "merchantCountry": "IRL",
    "currency": "EUR",
    "amount": "1000",
    "acquirerBin": "546283",
    "mcc": "5434",
    "installments": 2,
    "recurFrequency": 31,
    "recurringExpiry": "2024-12-12"
  },
  "areq": "{redacted_areq}"
}

2. 🎯 Risk Fields in the Response (Optional but Powerful!)

Issuers can now directly return risk evaluation outputs in the Card Link response. This puts the power of risk decisioning right in your hands!

Field	Values	Notes
`riskAction` 👑	`ACCEPT`, `CHALLENGE`, `REJECT`	Takes precedence over all other risk logic. Defaults to `EVALUATE` if omitted.
`riskScoreCategory` 📊	`LOW`, `MEDIUM`, `HIGH`	Broad risk classification
`riskScore` 🔢	`-100` to `100`	Granular numeric risk score

📋 Example Responses

🚧 Challenge Response

{
  "financialInstitutionId": "f88458df-20ea-49b7-b890-119c2f5e8c6e",
  "externalId": "fdhjkhkj34h3y4843343",
  "language": "en-EN",
  "riskAction": "CHALLENGE"
}

📈 Evaluate with Score

{
  "financialInstitutionId": "f88458df-20ea-49b7-b890-119c2f5e8c6e",
  "externalId": "fdhjkhkj34h3y4843343",
  "language": "en-EN",
  "riskScoreCategory": "MEDIUM",
  "riskScore": 60
}

💪 Benefits

🔗 Single Request, Maximum Power — Combines what previously required multiple API calls into one streamlined request.

🎛️ You're in Control — Issuers can directly influence risk outcomes by overriding Apata rules whenever needed.

🎯 Granular Scoring — Go beyond broad categories with precise numeric risk scores for finer decisioning.

🛠️ Migration Guide for Issuers

Ready to upgrade? Here's all you need to do:

✅ Update your integration to consume the new STANDARD_V1_WITH_RISK request format.
✅ Ensure your system can parse the new areq field.
✅ Implement support for returning the new risk fields in your response.

That's it — you're ready to unlock the future of real-time risk evaluation! 🚀🎊