What is a customer code in commercial card processing?

A customer code is a business reference carried with some commercial card transaction data. In Visa's U.S. Level II enhanced-data definition, examples include a cost center, general-ledger number, or order or invoice number. The reference helps an organization connect a payment to its own purchasing and accounting records.

The name can sound like a customer account number, but merchants should not assume the two are identical. The exact label, accepted format, and place where a user enters or supplies the value depend on the payment network, processor, gateway, platform, and buyer program involved.

A business reference, not a payment credential

A customer code is generally meant to describe the business purpose or internal owner of a purchase. For example, a buyer might provide a purchase-order reference, department code, project code, cost center, or invoice identifier so the transaction can be matched during reconciliation. Visa's April 2026 public rules specifically identify cost center, general-ledger number, and order or invoice number as customer-code examples within its U.S. Level II enhanced-data definition.

The code is not the card number, security code, merchant identification number, authorization result, or a password. It should be treated as a business-record field. Even when a screen calls the field a customer code, staff should use the buyer's approved reference and avoid placing sensitive payment credentials or personal information in it.

How the reference supports B2B records

Purchase identification

A buyer can use a purchase-order, order, or invoice reference to show which approved purchase the payment belongs to.

Department assignment

A cost center or department code can help the buyer route an expense to the appropriate internal team or budget record.

Accounting connection

A general-ledger or project reference can give accounting staff a starting point for matching the transaction to a business record.

The value is useful only when both sides understand the intended reference. A merchant should not invent a code merely to fill a field. If the buyer has not provided one, staff should follow the documented provider and customer workflow for an optional, blank, or unavailable value.

Customer code does not have one universal format

Current Visa documentation confirms that customer-code information can be associated with Level II capability, but that does not make every payment form or data-entry screen identical. Field length, allowed characters, required or optional status, validation behavior, and downstream reporting can vary. Another network or provider may use a different label for a similar business reference.

Before staff adopt a standard procedure, the merchant should obtain current documentation for the actual payment channel. The review should identify where the reference originates, who enters it, which formats are accepted, where it appears after the transaction, and what staff should do when the buyer does not supply a usable value.

A practical capture workflow

Ask for the business reference: Request the purchase-order, invoice, project, department, or other non-sensitive identifier the buyer uses for the purchase.
Confirm the approved field: Use the field and format documented for the merchant's current processor, gateway, virtual terminal, ecommerce system, or other payment workflow.
Keep source records aligned: Use the same reference consistently on the order, invoice, receipt, and internal reconciliation record where the business process allows it.
Review the saved result: Confirm that authorized staff can locate the reference in the transaction or reporting view used for reconciliation.
Define exception handling: Document who resolves missing, mistyped, duplicate, or buyer-disputed references without altering the underlying payment credential.

This workflow is operational guidance, not a statement that any particular provider supports a specific field or format. Merchants should test their own documented process with non-sensitive sample references before relying on it for routine work.

Privacy-safe handling matters

Use a customer code only for the minimum business reference needed to identify the purchase. Do not enter full card numbers, security codes, passwords, bank credentials, identity documents, tax identifiers, secret API keys, or unneeded personal information into the field. A reference that is safe for one organization's internal system may still reveal confidential project or customer details, so access should match staff responsibilities.

If a merchant needs help locating a customer-code field, share the product name, payment channel, screen label, and a redacted example with the provider's support team. Do not send live cardholder data or complete credentials through email, chat, screenshots, or a general contact form.

Related commercial payment resources

Start with the B2B, commercial cards, and Level 2/3 FAQ hub for connected concepts, and review what commercial cards are for the broader category. The payment processing glossary can clarify adjacent terminology, while the merchant statement help center provides general guidance for reviewing transaction records.

These resources are educational. They do not confirm a specific provider feature, data format, card program, or merchant setup. Current documentation for the merchant's processor and payment tools remains the operational source of truth.

Document the reference from entry to reporting

Choose one real business workflow, identify the reference the buyer supplies, and trace where authorized staff enter, verify, and reconcile it. Then ask the current or prospective payment provider to document the supported field name, format, and reporting location for that workflow.

Discuss a B2B payment workflow

Do not submit cardholder data, complete account numbers, passwords, bank credentials, identity documents, tax identifiers, or secret API keys through the general contact form.

To learn more about how TSYS can help improve the way your organization accepts payments, markets to new customers, or manages its HR responsibilities, get in touch by calling 585-981-8463 to get started.