Subscriptions
Connect plans, billing schedules, customer consent, payment status and service entitlement across the application and provider.
Connect the payment.
Complete the workflow.
RewardlyPAY · Adyen · Airwallex
EISOL connects payment acceptance with the order, customer and finance record—across stores, devices and digital channels.
OmnichannelReconciliationSubscriptionsTokenizationPayment-linked loyalty
The EISOL scope
Payment infrastructure, fitted to the operation.
EISOL designs and implements the connections around selected payment capabilities. Provider onboarding, regulated payment services and feature availability remain with the chosen payment provider.
01
Design
Map the payment moments, business rules, exception paths and system ownership before implementation.
02
Integrate
Connect supported terminals, checkout, APIs and webhooks with POS, commerce and custom applications.
03
Automate
Move verified payment, refund, fee and settlement data into finance and customer workflows.
RewardlyPAY · PaymentOS
One payment layer across every selling channel.
RewardlyPAY connects in-person and digital payment moments with Rewardly CommerceOS and supported external applications, keeping payment status close to the transaction that created it.
OmnichannelStore, mobile POS, online ordering and payment links
ReconciledConsistent order and payment references for automated matching
Workflow readySubscriptions, instalments and tokenized card-on-file journeys
Customer awareTrigger supported payment-linked loyalty journeys
RewardlyPAY · Omnichannel
Advanced payment workflows
Build the business rule around the payment event.
EISOL implements the application logic and data movement. Every workflow is subject to provider, payment-method, merchant-account and market availability.
Instalments
Present supported instalment choices in the selling flow and map authorisation, capture and settlement outcomes back to the order.
Card tokenization
Use provider-issued tokens for supported card-on-file, one-click or recurring journeys without storing raw card details in business applications.
Payment-linked loyalty
Connect verified payment events with customer recognition, rewards and campaigns while reducing manual membership steps at checkout.
Connected payment endpoint
Omnichannel acceptance
The terminal is one endpoint—not the whole system.
EISOL connects the endpoint to the order lifecycle so authorised, declined, cancelled and refunded outcomes can drive the correct operational response.
Context into payment
Pass the supported order amount, reference and transaction context from the selling system.
Status back to operations
Return payment outcomes to the POS, checkout or service workflow without duplicate entry.
Traceable exceptions
Keep refund, retry and unmatched-payment paths visible for support and finance teams.
Provider connectivity
Use the provider capabilities that fit the workflow.
EISOL scopes a defined integration rather than representing every product offered by Adyen or Airwallex.
ADYEN
Unified payment journeys
Relevant EISOL work can connect supported in-person and online payment flows, payment terminals, APIs, webhooks and tokenized recurring transactions with commerce applications.
- In-person and online payment integration
- Payment status and webhook handling
- Card tokenization and supported recurring flows
- Reconciliation-data integration
AIRWALLEX
Online payment and billing workflows
Relevant EISOL work can connect supported checkout, payment links, subscription billing and payment APIs with websites, applications and finance workflows.
- Online checkout integration
- Payment links and invoice-payment flows
- Supported subscription billing
- Payment and reconciliation-data integration
Actual products, markets, payment methods and workflows depend on provider approval, merchant configuration, technical availability and the agreed EISOL project scope.
Automated reconciliation
Close the loop from order to settlement.
A reconciled payment workflow gives operations and finance one traceable path for each sale and exception.
01OrderPOS, ecommerce or application reference
→
02PaymentAuthorisation, capture, refund or failure
→
03SettlementProvider settlement and fee records
→
04MatchAccounting, ERP and exception output
Where EISOL connects
The integration layer between commerce and finance.
The precise architecture depends on existing systems, provider interfaces and the controls required by the organisation.
01 / COMMERCE
POS + ordering
Lightspeed Retail X, Rewardly CommerceOS, ecommerce or custom applications.
02 / PAYMENT
Provider endpoints
RewardlyPAY and scoped Adyen or Airwallex interfaces.
03 / FINANCE
Reconciliation
Accounting, ERP, reporting and exception workflows.
04 / CUSTOMER
Loyalty
Payment-linked recognition and supported Rewardly LoyaltyOS journeys.
Payment integration questions
Define the boundary before building.
EISOL handles workflow design, solution integration, API and webhook connectivity, application development, transaction data mapping, reconciliation automation and connections to POS, commerce, loyalty, accounting or enterprise systems within the agreed scope.
No. The selected payment provider supplies the regulated payment service and merchant account. EISOL implements the surrounding workflow and supported systems integration.
EISOL can implement these workflows when they are supported by the selected provider, payment method, merchant configuration and market. The project defines consent, application state, API events and exception handling around the provider capability.
EISOL maps payment references, orders, refunds, fees and settlement data, then automates matching and exception handling between the payment provider and the relevant commerce, accounting or enterprise system.
Payment workflow design