Iconic Tyrant/ Corporate vision, AI orchestration, and ecosystem coordination under Tyrant standards. View the project list
ICONICGROUPPT ICONIC WIRA NIAGA Start a conversation
Back to the project list

Payment project

Project brief

Qrisbill

A payment project with a long-term roadmap toward a payment business that could compete with established providers such as Stripe.

Current statusPayment project / long-term roadmap Role in the ecosystemIt can draw on Vinexel’s technology and research base while remaining responsible for its own payment experience, risk boundaries, provider relationships, and operating decisions.

Project context

What this project is trying to make possible.

Payment project / long-term product direction

Qrisbill is a payment project focused on the practical work of moving money, managing payment flows, and building the foundations of a future payment business.

It can draw on Vinexel’s technology and research base while remaining responsible for its own payment experience, risk boundaries, provider relationships, and operating decisions.

Current statusPayment project / long-term product direction
Portfolio roleVisioniconic supports the project direction; Vinexel can provide underlying technology and research foundations as the product matures.

Project profile

The facts behind the project, with their evidence state.

Evidence level

Qrisbill is documented as a payment project inside the shared Visioniconic source boundary. Its distribution, funding, and operating ownership are not treated as settled without separate evidence.

1

Distribution and licensing

Product modelNot established
Distribution model not publicly declared

The project role is payment; its open-source, proprietary, or hybrid distribution model is not declared in the current project metadata.

License and distributionNot established
License or distribution status not publicly established

No reliable public evidence for this field was identified in the current audit.

2
Official websiteNot established
No official website separately established

No reliable public evidence for this field was identified in the current audit.

GitHub repositoryObserved
github.com/elwiraperdana/visioniconic (shared source repository)

Qrisbill appears as an application inside the shared checkout; a standalone public repository was not separately confirmed.

3

People and development

Named developer or teamNot established
Shared repository author metadata: vinexel; project-specific contributor roster not established

The local Git author label is not evidence of a complete named team or the number of people who worked on Qrisbill.

Development team sizeNot established
Total development team size not publicly established

No reliable public evidence for this field was identified in the current audit.

Development budgetNot established
Development budget not publicly established

No reliable public evidence for this field was identified in the current audit.

4

Ownership and business context

Parent or holding contextDeclared context
Iconic Tyrant / Tyrant Tech Imperials portfolio context

Declared as portfolio context or direction; this does not independently establish a legal or operational fact.

Client or commissioning companyNot established
Client or commissioning company not publicly established

No reliable public evidence for this field was identified in the current audit.

Ownership evidenceNot established
Legal ownership not publicly established

No reliable public evidence for this field was identified in the current audit.

Role in the ecosystem

One project can contain several systems.

1 systems documented

It can draw on Vinexel’s technology and research base while remaining responsible for its own payment experience, risk boundaries, provider relationships, and operating decisions.

Parent projectQrisbillPayment project
1Parent project implementation

Core project surface

Payment API, gateway adapters, finance services, node dashboard, admin tools, and developer utilities

Current statusPayment project / long-term roadmap
Role in the projectQrisbill is being developed around payment and billing capabilities. The ambition to compete with Stripe is a future direction, not a claim about current scale, reach, or market position.
View technical details for this system
Evidence levelConfirmed in application repository
Repository or source boundaryQrisbill Routes, Services, Models, payment adapters, and frontend documentation views
Runtime and execution contextPHP application running within the Vinexel project runtime
System boundary

API route → payment controller → orchestrator or finance service → gateway, ledger, webhook, and persistence boundaries

Modules and capabilities

8
Payment gateway interface and provider adapters
Gateway discovery and health checks
Payment and payout orchestration
Fee calculation and transaction services
Settlement, reconciliation, wallet, billing, and deposit services
Webhook delivery and retry handling
Node management, dashboard, KYC, audit trail, and developer console
API documentation and simulator surfaces

Representative interfaces

These are representative routes found in source, not a promise that this is an exhaustive API inventory.

5
GET/api/v1/channels

List available payment channels

POST/api/v1/payment/create

Create a payment transaction

POST/api/v1/payout/create

Create a payout transaction

GET/api/v1/transaction/status/{id}

Read transaction status

POST/callback/{provider}

Receive a provider callback

01

Confirmed evidence

  • GET /api/v1/channels is registered
  • POST /api/v1/payment/create is registered
  • POST /api/v1/payout/create is registered
  • GET /api/v1/transaction/status/{id} is registered
  • POST /callback/{provider} is registered
  • The source contains multiple gateway adapter classes and payment interfaces
02

Still open

  • Production readiness, provider contracts, live transaction volume, settlement performance, licensing, and uptime are not established by this public catalogue
  • The number of usable providers in a deployed environment is not inferred from the adapter count
  • Security and compliance text in product views is not treated as independent audit evidence
Current phase

Payment project with a long-term product roadmap

Next practical direction

Validate gateway contracts, payment lifecycle behavior, reconciliation, webhook reliability, compliance boundaries, and deployment readiness through controlled testing.

Longer-term possibility

Develop into a payment business with the product depth needed to compete with established providers such as Stripe.

Development strategy

A direction that can be tested and refined.

Development strategy

Strengthen the payment lifecycle from channel selection through transaction, payout, settlement, reconciliation, and reporting before pursuing broader market ambition.

01

Potential strengths

  • A clear problem space with recurring operational needs
  • A broad payment and billing direction that can be developed in stages
  • A long-term ambition to reach the product depth of established providers such as Stripe
02

Challenges and open considerations

  • Payment reliability, compliance, security, settlement, and provider dependency
  • Building trust before scale or market comparison is meaningful
  • Separating future ambition from evidence of current readiness

Current direction

A role, a current status, and a direction.

Current phase

Payment project with a long-term product roadmap

Next practical direction

Validate gateway contracts, payment lifecycle behavior, reconciliation, webhook reliability, compliance boundaries, and deployment readiness through controlled testing.

Longer-term possibility

Develop into a payment business with the product depth needed to compete with established providers such as Stripe.

Technical appendix

For readers who want the implementation context.

Confirmed in application repository

The following section is intentionally secondary. It records repository evidence and technical boundaries without asking every visitor to understand them first.

View technical evidence
Source surfacePayment API, gateway adapters, finance services, node dashboard, admin tools, and developer utilities

The repository exposes a substantial payment implementation surface. The future ambition to compete with Stripe remains a direction, not a current market or scale claim.

RuntimePHP application running within the Vinexel project runtime
Source surfaceQrisbill Routes, Services, Models, payment adapters, and frontend documentation views
Public surfacePayment, payout, channel, transaction status, and provider callback endpoints
Implementation scopeAPI route → payment controller → orchestrator or finance service → gateway, ledger, webhook, and persistence boundaries

Capabilities and modules

8
Payment gateway interface and provider adapters
Gateway discovery and health checks
Payment and payout orchestration
Fee calculation and transaction services
Settlement, reconciliation, wallet, billing, and deposit services
Webhook delivery and retry handling
Node management, dashboard, KYC, audit trail, and developer console
API documentation and simulator surfaces

Representative interfaces

These are representative routes found in source, not a promise that this is an exhaustive API inventory.

5
GET/api/v1/channelsList available payment channels
POST/api/v1/payment/createCreate a payment transaction
POST/api/v1/payout/createCreate a payout transaction
GET/api/v1/transaction/status/{id}Read transaction status
POST/callback/{provider}Receive a provider callback
01

Confirmed in repository

  • GET /api/v1/channels is registered
  • POST /api/v1/payment/create is registered
  • POST /api/v1/payout/create is registered
  • GET /api/v1/transaction/status/{id} is registered
  • POST /callback/{provider} is registered
  • The source contains multiple gateway adapter classes and payment interfaces
02

Not yet established

  • Production readiness, provider contracts, live transaction volume, settlement performance, licensing, and uptime are not established by this public catalogue
  • The number of usable providers in a deployed environment is not inferred from the adapter count
  • Security and compliance text in product views is not treated as independent audit evidence

Relationship to the portfolio

Relationship to the portfolio

Portfolio roleQrisbill
Vinexel

Can draw on the shared research and technology foundation while keeping payment operations specific to Qrisbill.

This brief reflects the current direction and evidence available for the project. It does not turn a possibility into a promise or a work-in-progress into a claim of production scale.

See contact context

Keep exploring

See the other
projects in the portfolio.

All projects