Structure program configuration
Document approved products, roles, controls and dependencies before cardholder operations begin.
Payments
Issuing Platform
Coordinate supported card-program configuration, lifecycle actions, transaction controls and operating events across the responsible participants.
For issuers, program managers, fintechs and card programs that need a clearer operating model across onboarding, card lifecycle and transaction activity.
Program configurationCardholder lifecycleTransaction controlsOperating visibility
Service outcomes
Coordinate card-program operations across responsible participants.
These are operating goals, not performance guarantees. Results depend on scope, participants, implementation and customer operations.
Coordinate lifecycle actions
Give supported onboarding, card, credential and status changes a defined owner and operating trail.
Connect transaction and authentication events
Relate agreed transaction controls, issuer decisions and eligible issuer-side authentication events to program operations.
Coverage & fit
Design the platform around the actual issuer and processor model.
Card products, schemes, processors, markets, credentials, controls and legal roles are confirmed for each proposed program.
Program setup
Supported product parameters, participant roles, controls, limits and operating procedures.
Cardholder lifecycle
Approved onboarding handoffs, card creation, activation, status, replacement and closure events.
Transaction operations
Supported controls, notifications, exceptions, disputes and account or card status interactions.
Authentication context
Eligible issuer-side ACS capability within the separate 3D Secure service where confirmed.
Issuer and scheme roles are not implied
Using an issuing platform does not state that Vellfi is the licensed issuer, scheme member, processor, program manager or custodian. Those roles must be expressly allocated.
Priority use cases
Use the platform where a card program needs coordinated lifecycle operations.
Fintech card program
A fintech needs a defined handoff among onboarding, program operations, issuer and processor services.
Program modernization
An existing program wants clearer lifecycle events and controls without assuming every participant can be replaced.
Multi-product portfolio
A program needs distinct configuration and operating rules for approved card products or customer segments.
Issuer-side authentication
A qualifying issuer or card program evaluates ACS responsibilities alongside broader issuing operations.
Core capabilities
Coordinate configuration, lifecycle and operating controls.
Capabilities are limited to the approved program design, processor interfaces and participant responsibilities included in scope.
Program configuration
Represent supported products, participant roles, status models, limits and operating policies.
Cardholder handoffs
Connect approved onboarding or eKYC outcomes to the cardholder creation process.
Card lifecycle events
Coordinate supported issue, activate, suspend, replace, renew and close actions.
Transaction controls
Apply supported program controls and pass relevant events to the responsible decisioning participant.
Notifications and exceptions
Return agreed lifecycle, transaction and operational events for customer service and program teams.
Dispute and authentication links
Connect separately scoped dispute and issuer-side 3D Secure operations where compatible.
Integration & deployment
Integrate around the issuer, processor and program operating model.
Technical and operational design covers system-of-record ownership, identifiers, credentials, lifecycle commands, event delivery, reconciliation and support escalation.
Request technical documentation →Processor connectivity
Map supported commands and events to the contracted processor or issuer-processing environment.
Onboarding handoff
Define the approved data and status passed from customer or eKYC workflows into cardholder operations.
Program operations
Connect customer service, risk, transaction, dispute and exception teams to agreed events and actions.
Controlled release
Test program, card and transaction scenarios with the relevant participants before production launch.
How it works
Move from approved program design to ongoing operations.
The flow is illustrative; legal issuance and processing actions remain with the allocated participants.
- 1
Configure. Agree products, participants, lifecycle statuses, controls and support procedures.
- 2
Onboard. Receive an approved cardholder or account handoff from the responsible process.
- 3
Issue. Send supported card creation or credential actions to the responsible participant.
- 4
Control. Apply supported lifecycle and transaction controls and coordinate authentication where scoped.
- 5
Operate. Return events, exceptions and records to program, risk, support and dispute teams.
Illustrative scenario—not a customer case study
A fintech is preparing a card program with several operating partners.
Context
Onboarding, processor commands, card status, authentication and customer support are being designed in separate workstreams.
ChallengeOwnership of lifecycle decisions, data handoffs and exception handling is unclear before launch.
Possible approach
Vellfi maps the supported program configuration, lifecycle actions, event model and participant responsibilities, then connects approved interfaces in controlled stages.
Potential operating effectThe program has a defined operating model and system handoffs. Issuance approval, scheme participation and launch timing remain with the relevant parties.
Responsibilities & availability
Allocate issuing responsibilities before implementation.
Program owner
Owns product design, customer proposition, lawful basis, disclosures and approved program policy.
Issuer / program manager
Performs the legal and scheme roles allocated under the applicable arrangements.
Processor and partners
Provide contracted processing, card, fulfilment, authentication or other operational functions.
Vellfi
Provides only the supported technology configuration, integration and operating events included in scope.
Program approval is external
No page statement guarantees issuer approval, scheme participation, processor support, card availability, regulatory permission or launch timing.
Next step
Define the card-program operating model.
Share the proposed products, issuer and processor relationships, lifecycle requirements and operating responsibilities without sending cardholder documents through the website.
FAQ
Issuing Platform: common questions
Who is the Issuing Platform for?
It is for issuers, program managers, fintechs and card programs evaluating supported configuration, lifecycle, control and operating workflows.
Does Vellfi become the card issuer?
Not by providing this platform. The licensed issuer and other legal or scheme roles must be identified in the applicable arrangements.
Which card schemes or processors are supported?
Compatibility is not stated universally. The proposed scheme, processor, market, product and interface must be confirmed.
Can eKYC connect to the platform?
Potentially, where eKYC is separately scoped and the approved onboarding outcome can be passed into the cardholder workflow.
How does 3D Secure ACS relate to issuing?
Eligible issuer-side ACS capability can support online cardholder authentication, but it is a separate service and deployment scope.
Are physical and virtual cards included?
Only card forms, fulfilment responsibilities and interfaces expressly confirmed for the proposed program are included.
What is needed before scoping?
Program products, target markets, issuer and processor relationships, lifecycle actions, controls, event requirements and support model are useful inputs.