Dynamic Descriptors

Specifies the card acceptor descriptor details to send to the cardholder's issuing bank which they can use to describe the transaction on the cardholder's statement, mobile banking etc.

Dynamic Descriptors are specified by the field descriptor of type Hash. descriptor must contain either the fields name and location, or else the field raw (if supported), all having type String.

🚧

Warning:

• The descriptor details passed on by Fat Zebra may be truncated or formatted differently based on how each cardholder's issuing bank chooses to format and display these values to their customers. An issuing bank may also format the same transaction description differently in different places, e.g. paper statement, digital statement, mobile app, online banking etc.
• Support for the raw descriptor field is not yet implemented for all upstream processors. Currently, it will only be used when provided in transactions processed by Fiserv.

{
  "extra": {
    "descriptor": {
      "name": "Biz Name Pty",
      "location": "Surry Hills"
    }
  }
}

{
  "extra": {
    "descriptor": {
      "raw": "Biz Name Pty Surry Hills NSW AU"
    }
  }
}

Notes for Bill Payment Service Providers/Consumer Bill Payment Services

Merchants who process transactions for bill payments on behalf of other companies, known as Bill Payment Service Providers or Consumer Bill Payment Services, are required to format their descriptor according to scheme requirements, as follows:

BPSP NAME*MERCHANT NAME

In order to do this, the raw descriptor field must be used, as per the following example:

{
  "extra": {
    "descriptor": {
      "raw": "PAYCORP*Clean Co"
    }
  }
}