On This Page
REST API
orderInformation. invoiceDetails.
purchaseOrderNumber
The values used by your customer to identify the order.
This field is supported only for
Chase Paymentech Solutions
, Elavon Americas
, FDC Compass
, FDC Nashville Global
,
GPN
, Visa Platform Connect
, OmniPay Direct
, RBS WorldPay Atlanta
,
TSYS Acquiring Solutions
, and Worldpay VAP
.This value is typically a purchase order number.
It is recommended that you do not populate the field with all zeros or nines.
IMPORTANT
Only alphanumeric characters are accepted on
FDC Nashville Global
. Do not include hyphens or other non-alphanumeric characters.- FDC Nashville Global
- You must provide a value in this field or in theclientReferenceInformation.codefield.
Specifications
- Data Type:String
- Data Length:
- : 17American Express Direct
- : 17Elavon Americas
- : 17Visa Platform Connect
- : 17GPX
- : 17Worldpay VAP
- : 17 for Mastercard, 25 for VisaGPN
- : 17 for Mastercard, 25 for VisaOmniPay Direct
- All other processors:25
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:
- does not applyAmerican Express Direct:
- Customer Reference NumberChase Paymentech Solutions:
- Purchase IdentifierElavon Americas:
- Customer Reference NumberFDC Compass:
- Customer CodeFDC Nashville Global:
- does not applyFDMS Nashville:
- does not applyFDMS South:
- Market Data - Customer Code and Reference NumberGPN:
- Customer Code / Customer Reference IDOmniPay Direct:
- PC2 Customer IDRBS WorldPay Atlanta:
- does not applyTSYS Acquiring Solutions:
- customerCodeVisa Platform Connect:
- customerReferenceWorldpay VAP: