Service overview
Issuer, BIN, scheme, processor, technology, reporting and settlement coordination for approved payment programs.
Phoenix supports eligible payment infrastructure mandates through approved banking, scheme, processing and compliance arrangements. The focus is the delivery model: the parties, integrations and operating controls required to support a documented program.
Program availability, issuer role, BIN sponsorship, scheme participation, processing model, settlement mechanics, reporting and controls are confirmed through approved partner arrangements and written documentation.
Phoenix does not represent that any Visa, Mastercard, issuer, BIN sponsor, processor or settlement arrangement is available unless the relevant approvals and agreements are in place for the specific mandate.
Define the transaction and data flows
Map authorisation, clearing, settlement and reporting between the relevant systems and counterparties. Review the visibility required by the program operator and approved participants.
Confirm the control responsibilities
Identify which party supplies security, access controls, transaction monitoring and incident-response processes. Confirm these responsibilities in the approved operating arrangements.
Integration and delivery scope
Issuer, BIN and scheme coordination
Review the proposed issuer role, sponsorship and scheme participation for the mandate, including required approvals and program conditions.
Processor and technology integration
Define processing interfaces, supported channels and integration requirements. Accounting, ERP or reporting connections are assessed against the approved scope and partner systems.
Settlement and reconciliation interfaces
Clarify banking and processing counterparties, transaction records and reconciliation workflows. Settlement Solutions describes the separate routing, reconciliation, reporting and dispute-support scope.
Operating controls
The infrastructure review considers the security and continuity arrangements required for the proposed program, including transaction protection, access controls, monitoring and partner responsibilities. Available features depend on the systems and arrangements approved for the mandate.
Access and fraud monitoring
Review permitted users and channels, monitoring rules, risk alerts, escalation paths and response responsibilities. Acceptance, currencies and geography remain subject to the applicable partners and approvals.
Reporting and oversight
Specify transaction, settlement and program reporting, access permissions, reconciliation needs and oversight records. Confirm the data scope and reporting available through the selected partners.
Governance and compliance
Client due diligence, AML/CFT, sanctions, data protection, scheme rules and relevant regulatory requirements form part of the assessment. Document operational responsibilities and required approvals before activation.
Separate the infrastructure from the card use case
For prepaid, corporate spending, loyalty and co-branded program design, see Card & Payment Program Solutions. For accepting customer payments, see Merchant Acquiring. This page addresses the infrastructure that supports an approved program.
Plan a payment infrastructure enquiry
For institutions and program operators coordinating the delivery of an approved payment program.
Scope to discuss
- Map issuer, BIN, scheme, processor and technology responsibilities.
- Review integration, authorisation, clearing and settlement interfaces.
- Define access controls, risk monitoring, reporting and operating oversight.
Infrastructure coordination depends on documented partner roles and approvals. The client-facing card use cases are described under Card & Payment Program Solutions.
Information to prepare
Prepare the program design, existing and proposed partners, transaction and data flows, required integrations, reporting needs and approval status.
Next steps and fees
Send an initial enquiry with the service and your objective. Phoenix reviews the proposed scope, eligibility and information requirements before a mandate is agreed. Execution is subject to due diligence, documented responsibilities and the relevant approvals.
Fees are assessed by mandate scope, complexity, due diligence and execution requirements. Review the Fees & Engagement Terms before discussing a proposal.