Who owns the economics?
At scale, pricing, fees, commissions, reserves and partner arrangements deserve a clear model and records finance can reconcile.
We help platforms turn payments into a business. Start with a PSP for speed; add control over economics, operations and providers as your model evolves.
Why we exist
A PSP is often the fastest way to launch, and it may remain the right processing partner. As volume and complexity grow, the decisions that shape a payment business move above the processor: pricing, routing, onboarding, risk workflows, payouts, ledger and reconciliation.
Amaryllis provides the technology layer that brings those decisions and records together. Our engineers adapt its integrations and workflows to each customer’s requirements. A company can keep its PSP, add providers, or build the operating foundation for PayFac or Merchant of Record arrangements without treating every new step as a complete rebuild.
The idea behind Amaryllis
At scale, pricing, fees, commissions, reserves and partner arrangements deserve a clear model and records finance can reconcile.
Merchant onboarding, risk review, disputes and payouts need workflows matched to your contracts and markets.
Some businesses need orchestration across providers. Others need PayFac operations or a ledger and settlement layer for MoR-style complexity. There is no forced end state.
How we got here
Ori Hay and Adi Ekshtain worked together on payment technology before starting Amaryllis. Adi helped develop an early commercial mobile-payment system. Ori later started a payment service provider and brought Adi into the team. Together they worked with Microsoft on a .NET payment gateway and received recognition for the project.
They founded Amaryllis in 2011 after seeing the same pattern across the industry: businesses building similar payment systems from scratch. The goal was to turn knowledge from payment gateways, mobile payments and billing into a platform that could be tailored to different operating models.
That goal still guides the product. Customers now need to connect providers, merchant operations and financial records while keeping control of how their business develops.
CEO & Co-Founder
Co-Founder
What we build
Amaryllis engineers connect and configure the relevant capabilities for each implementation. Clients operate the delivered solution while our team handles configuration and extensions.
Represent billing plans, splits, commissions, partner terms and reserves in a clear operating model.
Connect processing partners and payment methods with routing and reporting rules that suit your business.
Coordinate payout schedules, balances and seller or property settlements under agreed controls.
Bring transactions, fees, adjustments, refunds and settlements into records finance can trace.
Connect merchant reviews, alerts, disputes and applicable compliance steps according to the implementation scope.
Fit payment and operational systems together through the interfaces and data flows your teams require.
Two journeys. One platform.
Launch with a PSP. As payment volume grows, add provider options, merchant operations and greater visibility into pricing, fees and payouts. Choose PayFac capabilities only when the business case and operating responsibilities fit.
Start with finance and settlement needs. Connect transactions across providers, entities and properties; build reconciliation and supplier settlement workflows for complex enterprise or hospitality operations.
Our commitment
Security and privacy shape how payment systems are built and operated. We design implementations around PCI DSS requirements and applicable privacy obligations, including GDPR and CCPA. Ask our team for the scope and current supporting documentation for compliance and SOC controls relevant to your implementation.
Co-Founder Adi Ekshtain’s participation in Forbes Technology Council is one way Amaryllis stays involved in the wider payments and technology conversation.