# Glossary

Understand the terms used throughout Payment Network.

| Term | Definition |
|  --- | --- |
| Access Token | Security token obtained through OAuth 2.0 authentication and used to authorize API requests. |
| Acknowledgement | Update returned by a lockbox provider indicating the outcome or processing state of a payment delivered through Payment Network. |
| API | Application Programming Interface. A set of endpoints that enable applications to interact with Payment Network services. |
| Authentication | The process of verifying an application's identity before granting access to Payment Network services. |
| businessPartner | Unique identifier assigned to your organization for Payment Network API requests. |
| Client Credentials | OAuth 2.0 authentication grant type used for server-to-server communication. |
| Client ID | Identifier used to authenticate an application when requesting access tokens. |
| Client Secret | Confidential credential associated with a Client ID. |
| Completed | Terminal payment status indicating successful processing. |
| Deluxe Directory Network (DDN) | Directory service used to retrieve lockbox information and support destination validation and pre-matching workflows. |
| Directory Match | Process of identifying a potential lockbox destination using information maintained in the Deluxe Directory Network (DDN). |
| Disburser | Organization that submits payment files to Payment Network. |
| Disburser Service | Primary Payment Network API service used to submit payment files, retrieve payment information, retrieve processing errors, and monitor payment status. |
| Exception | Payment or processing event requiring investigation or corrective action. |
| Failed | Terminal payment status indicating that processing could not be completed successfully. |
| File GUID | Unique identifier assigned to a submitted payment file and used when retrieving file status and payment status information. |
| Fulfillment | Process of producing, preparing, and delivering payment artifacts through a selected workflow. |
| Fulfillment Workflow | Method used to deliver a payment, such as Print + Scan or Print + Mail. |
| In Production | Payment status indicating that fulfillment activities are actively occurring. |
| Lockbox | Payment-processing destination used to receive and process remittance information. |
| Lockbox Destination | Lockbox location selected by Payment Network for payment package delivery and processing. |
| Lockbox Provider | Organization that receives payment packages from Payment Network, processes transactions, and returns status information and acknowledgements. |
| OAuth 2.0 | Authorization framework used by Payment Network for authentication and access control. |
| OAuth Access Token | Temporary access credential obtained through OAuth 2.0 and included in API requests using the Bearer authentication scheme. |
| Payee | Recipient of a payment. |
| Payer | Organization or individual sending a payment. |
| Payment File | CSV file containing one or more payment records submitted to Payment Network. |
| Payment Lifecycle | End-to-end journey of a payment from submission through fulfillment, delivery, status updates, and reconciliation. |
| Payment Network | Platform used to submit payments, coordinate fulfillment, route payment packages, track processing status, and support reconciliation workflows. |
| Payment Package | Collection of payment information, payment artifacts, images, and metadata delivered to a lockbox provider for processing. |
| Payment Record | Individual payment entry within a payment file. |
| Payment Status | Value that represents the current processing stage of a payment. |
| Pre-Matching | Process of retrieving lockbox information from DDN before payment submission to support destination validation and planning. |
| Print + Mail | Fulfillment workflow that prints and mails payment packages directly to recipients. |
| Print + Scan | Fulfillment workflow in which Payment Network coordinates fulfillment, associates payment artifacts with payment data, and delivers a payment package electronically to a lockbox provider. |
| Processing Exception | Issue encountered during routing, fulfillment, delivery, or other payment-processing activities that may require investigation or corrective action. |
| Production Environment | Live Payment Network environment used to process production payments. |
| Record Identifier | Unique value used to identify a payment record within a payment file. |
| Reconciliation | Process of comparing submitted payments with returned status information and processing outcomes. |
| Routing | Process performed by Payment Network to determine the appropriate destination for a submitted payment. |
| Sandbox (XUAT) | Non-production environment used for development, testing, and validation. |
| Status Transition | Change from one payment status to another during processing. |
| Sub-Status | Additional status detail returned alongside a payment status. |
| Support Case | Request submitted to Deluxe Support for assistance with an issue. |
| Terminal Status | Status indicating that processing has completed and no additional status changes are expected. |
| Tracking Identifier | Identifier used to retrieve, monitor, and troubleshoot submitted payment files and payment records. |
| Validation | Process of checking file structure, payment data, routing information, and business rules. |
| Validation Error | Error indicating submitted data does not comply with Payment Network requirements. |
| XUAT | Payment Network sandbox environment used for testing prior to production deployment. |