Enterprise / Enterprise Payments
Payments designed for organizational control.
First Digital Pay Enterprise Payments is designed for organizations that need payment activity to operate within defined processes, responsibilities and controls.
The payment remains connected to its commercial purpose while the organization maintains visibility over how it moves through the operating workflow.
Availability varies by product, jurisdiction, configuration and eligibility.
Enterprise payment detail
- Payment reference
- PAY-2026-2207
- Commercial reference
- PO-51930
- Payment state
- Processing
- Workflow state
- Awaiting authorization
- Required action
- Authorization
- Settlement state
- Not yet initiated
- Last updated
- 29 Sep 2026, 10:42
Illustrative example
A payment can be part of a larger process.
- 01
Initiate
An eligible payment workflow begins.
- 02
Review
Where configured
Information is reviewed.
- 03
Authorize
Where configured
Authorization is recorded.
- 04
Process
The payment moves through applicable processing.
- 05
Monitor
Status remains visible to the organization.
- 06
Settle
Processed activity relates to settlement.
- 07
Reconcile
Settlement is matched to the payment.
Review and authorization apply where configured. Not every payment requires every stage, and payments are not necessarily manually approved. Actual workflow depends upon product configuration, organizational requirements and eligibility.
Payment status and workflow status serve different purposes.
A payment can be processing while the organization's workflow is still waiting on an authorization, and before any settlement has begun. These are separate operational concepts, so they are shown separately rather than collapsed into one status.
Payment status
Processing
Where the payment itself stands in processing.
Workflow status
Awaiting authorization
Where the organization's configured process stands.
Settlement status
Not yet initiated
Whether settlement activity has begun for this payment.
Illustrative example. The same payment, described by three separate status families.
Put the right responsibilities around the payment.
- Initiator
- Creates or begins an eligible payment workflow.
- Reviewer
- Reviews information where the configured workflow requires it.
- Authorizer
- Provides authorization where the configured workflow requires it.
- Operations
- Follows processing and exceptions.
- Finance
- Maintains visibility into settlement and reconciliation.
These are conceptual responsibilities, not finalized First Digital Pay roles or permission sets. Role and permission functionality remains subject to product design and configuration.
Controls should clarify the payment, not hide it.
The organizational workflow sits around the payment record. Commercial, payment, processing, settlement and reconciliation references stay visible while the workflow progresses.
Enterprise workflow
- Initiated
- Review completed
- Awaiting authorization
Transaction record
- Commercial reference
- PO-51930
- Payment reference
- PAY-2026-2207
- Processing
- PRC-2026-2207 · Processing
- Settlement relationship
- Not yet allocated
- Reconciliation relationship
- Pending settlement
Illustrative example. The workflow wraps the transaction record; it does not replace it.
Understand how the payment moved through the organization.
A history of workflow and transaction events, kept separate from the payment's current state.
Workflow history · PAY-2026-2207
- 01
Payment initiated
Performed by: Initiator (illustrative)
- 02
Review completed
Performed by: Reviewer (illustrative)
- 03
Authorization recorded
Performed by: Authorizer (illustrative)
- 04
Processing started
Performed by: System
- 05
Processing updated
Performed by: System
- 06
Settlement recorded
Performed by: System
- 07
Reconciliation updated
Performed by: Finance (illustrative)
Illustrative example. Conceptual history; not a claim of legal immutability or regulatory audit compliance.
Know when the workflow needs attention.
- Action required
- A configured step needs a response before the workflow can continue.
- Information required
- Additional information is needed to complete a step.
- Awaiting authorization
- The workflow is waiting for a configured authorization.
- Processing
- The payment is moving through applicable processing.
- No action required
- Nothing currently needs attention from the organization.
Conceptual states. Exceptions are surfaced for the organization to address; resolution is not automated.
Organizational control does not end at processing.
Workflow controls surround payment operations while the underlying First Digital Pay transaction architecture remains consistent.
Enterprise workflow
- 01 · INVCommercial reference
- 02 · PAYPayment
- 03 · PRCProcessing
- 04 · STLSettlement
- 05 · RECReconciliation
Illustrative example. Reference prefixes are working conventions, not final technical identifiers.
Connect payment workflows to your operating environment.
Enterprise Payments should ultimately support appropriate integration with organizational systems, so workflows can begin from, and report back to, the systems an organization already uses. Specific interfaces and supported systems are subject to final technical implementation and product availability.
See what needs attention across payment operations.
Payment operations
- Awaiting action
- 3
- Under review
- 2
- Processing
- 5
- Settlement activity
- 1 in preparation
- Reconciliation state
- 1 exception
Illustrative example. Record counts are illustrative; not performance analytics.
Build payment workflows around your organization.
Tell us about your payment processes, approval requirements, settlement needs and integration environment.
Availability varies by product, jurisdiction, configuration and eligibility.