invoiceHeader_userPO
Value used by your customer to identify the order.
This value is typically a purchase order number.
Cybersource
recommends that you do not populate the field with all zeros or nines.This field is available only on the
Barclays
, Chase Paymentech Solutions
, Elavon Americas
, FDC Compass
,
FDC Nashville Global
, GPN
, OmniPay Direct
,
RBS WorldPay Atlanta
, TSYS Acquiring Solutions
, Visa Platform Connect
, and
Worldpay VAP
processors.- FDC Nashville Global
- Only alphanumeric characters are accepted onFDC Nashville Global. Do not include hyphens or other non-alphanumeric characters. You must provide a value in this field or in themerchantReferenceCodefield.
Specifications
- Data Type:String
- Data Length
- American Express Direct: 17
- Barclays: 25
- Chase Paymentech Solutions: 25
- Elavon Americas: 17
- FDC Compass: 25
- FDC Nashville Global: 25
- GPN: 17 for Mastercard, 25 for Visa
- OmniPay Direct: 17 for Mastercard, 25 for Visa
- FDMS Nashville: 25
- FDMS South: 25
- RBS WorldPay Atlanta: 25
- Visa Platform Connect: 17
- TSYS Acquiring Solutions: 25
- Worldpay VAP: 17
Mapping Information
- REST API Field:orderInformation.invoiceDetails.purchaseOrderNumber
- SCMP API Field:user_po
- Simple Order API Field:invoiceHeader_userPO
Processor Field Names
This list provides the Level II/Level III processor field name for each processor that
supports Level II or Level III data:
- American Express Direct: does not apply
- Chase Paymentech Solutions: Customer Reference Number
- Elavon Americas: Purchase Identifier
- FDC Compass: Customer Reference Number
- FDC Nashville Global: Customer Code
- FDMS Nashville: does not apply
- FDMS South: does not apply
- GPN: Market Data - Customer Code and Reference Number
- OmniPay Direct: Customer Code / Customer Reference ID
- RBS WorldPay Atlanta: PC2 Customer ID
- TSYS Acquiring Solutions: does not apply
- Visa Platform Connect: customerCode
- Worldpay VAP: customerReference