On This Page

Merchant Descriptors Developer Guide

This section provides you with information about this developer guide.
Audience and Purpose
This guide is written for application developers who want to use the
REST API
 to integrate merchant descriptors into their payment acceptance system.
Implementing merchant descriptors requires software development skills. You must write code that uses the API request fields to include merchant descriptor fields in payment service requests.
Conventions
These statements are used in guides to bring attention to critical information:
IMPORTANT
An
Important
 statement contains information essential to successfully completing a task or learning a concept.
WARNING
A
Warning
 contains information or instructions, which, if not heeded, can result in a security risk, irreversible loss of data, or significant cost in time or revenue or both.
Customer Support
For support information about any service, visit the Support Center:

Recent Revisions to This Document

25.05.01

Initial release.

Barclays
 Merchant Descriptors

This feature enables you to submit merchant descriptor values that appear on a cardholder's statement.

Prerequisite

Before including merchant descriptors in your requests, you must be boarded to the
Barclays
 multi-currency platform.

Services

  • Capture
  • Refund

Merchant Descriptor Fields for
Barclays

merchantInformation.merchantDescriptor.name
Description:
merchant description that appears on the cardholder's statement. When you include more than one consecutive space, extra spaces are removed. Before you send merchant descriptor to the processor, all non-alphanumeric characters are replaced with
?
.
Required or Optional:
 required for capture and refund services when the merchant descriptor contact is included in the request.
Data Type:
string
Data Length:
 23
merchantInformation.merchantDescriptor.contact
Description:
merchant contact information, such as a phone number, that appears on the cardholder's statement. When you include more than one consecutive space, extra spaces are removed. Before you send merchant descriptor to the processor, all non-alphanumeric characters are replaced with
?
.
Required or Optional:
 optional for capture and refund services.
Data Type:
 string
Data Length:
 13
Payment Descriptor Request
 {
  "clientReferenceInformation": {
    "code": "TC50171_3"
  },
  "orderInformation": {
    "amountDetails": {
      "totalAmount": "102.21",
      "currency": "GBP"
    }
  },
  "merchantInformation": {
    "merchantDescriptor": {
      "name": "barclaystestdescriptor",
      "contact": "07854806658"
    }
  }
}
Payment Descriptor Response
  {
  "_links": {
    "void": {
      "method": "POST",
      "href": "/pts/v2/captures/7479964660936642304805/voids"
    },
    "self": {
      "method": "GET",
      "href": "/pts/v2/captures/7479964660936642304805"
    }
  },
  "clientReferenceInformation": {
    "code": "TC50171_3"
  },
  "id": "7479964660936642304805",
  "orderInformation": {
    "amountDetails": {
      "totalAmount": "102.21",
      "currency": "GBP"
    }
  },
  "reconciliationId": "7026822076",
  "status": "PENDING",
  "submitTimeUtc": "2025-05-23T10:34:26Z"
}