{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://raw.githubusercontent.com/api-evangelist/cm-com/main/json-schema/cm-com-transaction-response-schema.json",
  "title": "Transaction response",
  "x-generated": "2026-10-13",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/cm-com-verification-iban-verification-v1-openapi.yml#/components/schemas/TransactionResponse",
  "required": [
    "issuer_authentication_url",
    "merchant_reference",
    "transaction_id"
  ],
  "type": "object",
  "properties": {
    "transaction_id": {
      "$ref": "#/$defs/TransactionID"
    },
    "issuer_authentication_url": {
      "maxLength": 512,
      "type": "string",
      "description": "The location where you should forward the customer to. They will begin their bank authentication here.\n"
    },
    "merchant_reference": {
      "maxLength": 35,
      "pattern": "^[a-zA-Z0-9]+$",
      "type": "string",
      "description": "An internal reference id for accounting purposes"
    }
  },
  "$defs": {
    "TransactionID": {
      "maxLength": 16,
      "minLength": 16,
      "pattern": "^[0-9]+$",
      "type": "string",
      "description": "A token for this transaction. You should store this with your session data, so that at any point, you can make a callback to the CM api and retrieve the status and/or results. Note that it is not guaranteed that your user will return to you via your merchant_return_url. A connection might be dropped, a user might accidentally close a window, or they might trigger the back button and return that way. This id is the only way you can retrieve any information in that case.\n"
    }
  }
}