On This Page
REST API

clientReferenceInformation. code

Order reference or tracking number that you generate.
Provide a unique value for each transaction so that you can perform meaningful searches for the transaction. Refer to the
Getting Started with
Cybersource
 Advanced
 guide.
IMPORTANT
Depending on the values in your
Cybersource
 account, there might be a requirement for this field's value to be unique within a 15-minute period. Contact customer support to find out whether this requirement applies to your
Cybersource
 account.
PIN Debit Transactions
Requests for PIN debit reversals must include the same merchant reference number that was used in the transaction that is being reversed.
FDC Nashville Global
During card-not-present transactions, certain circumstances can cause the processor to truncate this value to 15 or 17 characters for Level II and Level III processing, which can cause a discrepancy between the value you submit and the value included in some processor reports.
FDC Nashville Global
During card-present transactions, when you do not send a valid value, one is created for you. However, the value is not returned, so you cannot use it to track the order.
SIX
When a card-present request does not include a merchant reference number, this value is provided by the client software that is installed on the POS terminal.

Specifications

  • Data Type:
     String
  • Data Length:
     50
  • Data Length:
    • Asia, Middle East, and Africa Gateway
      Data Length:
       40
    • China UnionPay
      Data Length:
       12
    • Elavon Americas
      Data Length:
       39
    • FDC Nashville Global
      Data Length:
       8
    • RuPay
      Data Length:
       24 (Credit Services)
    • RuPay
      Data Length:
       50 (Other services)
    • All Other Processor's Data Length:
       8

Mapping Information

  • REST API Field:
    clientReferenceInformation.code
  • SCMP API Field:
    merchant_ref_number
  • Simple Order API Field:
    merchantReferenceCode