For vendors accepting government purchase cards from federal agencies such as the Department of Veterans Affairs, properly capturing and transmitting purchase order information can be an important part of both transaction reconciliation and Level 3 interchange qualification. The challenge is that simply having a gateway that supports Level 3 does not necessarily mean every required data field is being captured and transmitted correctly. Purchase order or customer-code information must be properly mapped through the payment environment — and merchants should verify how that information is being transmitted rather than assuming the account is configured correctly.

What Is a Government Purchase Card PO Descriptor?

A government purchase card PO descriptor refers to the Purchase Order number or Customer Code that is transmitted electronically with a credit card transaction as part of the Level 3 data submission. When a federal agency purchasing agent uses a government purchase card — also called a G-Card or GSA SmartPay card — including this information with the transaction supports the auditing and reconciliation processes that agencies use to manage purchase card spending.

This field must be enabled and configured correctly in the merchant’s payment environment. Without it, the transaction may still process — but the purchasing agent’s ability to automatically reconcile the charge in their procurement system can be affected.

Three Reasons the Government Purchase Card PO Descriptor Matters

The government purchase card PO descriptor affects vendors selling to federal agencies in three meaningful ways — each with real operational or financial consequences.

• Without the PO information — the purchasing agent may need to manually research each unmatched charge to determine which transaction corresponds to which purchase order, creating additional administrative work
• With the PO information transmitted correctly — the agency’s system can match the charge to the open purchase order automatically, with no manual intervention required

How the Government Purchase Card PO Descriptor Works in Practice

When a government purchasing agent places an order, they typically provide a Purchase Order number or Customer Code. This information needs to be captured at the time of the transaction and transmitted through the payment environment as part of the Level 3 data submission.

The payment system — whether a virtual terminal, integrated gateway, or compatible point-of-sale environment — is responsible for capturing and transmitting this field. Not all payment environments are configured to handle this correctly even when they technically support Level 3 data, and the government purchase card PO descriptor field must be specifically enabled and mapped to capture the information on each transaction.

Government Purchase Card PO Descriptor Considerations for VA Vendors

The Department of Veterans Affairs has detailed purchase card auditing and reconciliation processes. VA purchasing agents work within internal systems that are designed to match card statement transactions to open obligations and purchase orders.

For vendors selling to the VA, ensuring that the government purchase card PO descriptor is transmitting correctly is a practical consideration — both for making the purchasing agent’s reconciliation process smoother and for maximizing the opportunity to qualify for Level 3 interchange rates on eligible transactions.

How to Confirm the Government Purchase Card PO Descriptor Is Working

The most reliable way to confirm the government purchase card PO information is transmitting correctly is to run a test or live transaction and verify the resulting transaction data with your payment provider. If the setup is intended to display the PO number on the purchasing agent’s card statement, that should also be specifically tested and confirmed — how PO information appears in the transaction data versus on the cardholder statement can vary depending on how the payment environment is configured.

• Verify the payment environment supports Level 3 data submission — not all payment setups transmit enhanced data fields even when technically capable
• Confirm the PO descriptor field is enabled and mapped — general Level 3 support does not guarantee every field is active and configured
• Test a transaction and review the statement — confirm the PO number appears correctly rather than assuming
• Check processing statements for interchange qualification — if government card transactions are not qualifying at enhanced data rates, it may indicate required fields are not transmitting correctly
• Ask your processor specifically — can the PO number provided by the purchasing agent be captured and transmitted dynamically on each transaction

What Correct Government Purchase Card PO Descriptor Setup Looks Like

A properly configured government purchase card account captures the PO number or Customer Code at the time of the transaction and transmits it as part of the Level 3 data submission. The field populates based on what the purchasing agent provides for each transaction — not as a static value that is the same on every charge.

Revolution Payments configures government contractor merchant accounts with Level 3 data submission in mind — including the government purchase card PO descriptor field. Accounts are reviewed to confirm that the required data fields are transmitting correctly and that government card transactions have the best opportunity to qualify at Level 3 interchange rates.

For government contractors who are already processing and unsure whether the government purchase card PO descriptor is configured correctly — a statement review can help identify whether transactions are qualifying at the interchange level expected for properly submitted government card data.