Building an Ecommerce Platform Around Flexible Payments and Complex Operations

An established UK retailer needed technology capable of supporting far more than a conventional online checkout.

Its commercial model combined ecommerce, flexible ways to pay, recurring collections, order management, fulfilment, delivery and ongoing customer service.

Irvine-David designed and built a bespoke digital platform connecting those activities from the initial customer order through payment, fulfilment and aftercare.

The result is a business-critical system that supports multiple payment methods and providers, reduces manual administration, improves operational visibility and gives the retailer a platform that can continue evolving with the business.

The Client

Our client is an established UK retail business selling products directly to consumers through a combination of digital and assisted sales channels.

A central part of its proposition is giving customers a convenient and flexible purchasing experience.

Customers can choose from different payment methods depending on the purchase and their circumstances.

Behind that apparently simple proposition sits a complex operational process.

Orders must be created and confirmed, payments processed, products fulfilled, deliveries coordinated and customer accounts managed throughout the relationship.

The business needed technology designed around that complete journey rather than a collection of systems addressing individual stages in isolation.

Irvine-David created the platform from scratch and has continued to provide hands-on development and technology leadership as the business, its processes and the payments landscape have evolved.

The Challenge

Many ecommerce systems assume a straightforward transaction.

A customer selects a product, pays the full amount and receives the goods.

That model did not reflect the way this business operated.

The platform needed to support customers whose orders might involve:

·        different payment methods and collection arrangements;

·        one-off and recurring transactions;

·        changes to customer payment details or arrangements;

·        orders requiring several stages of preparation and fulfilment;

·        delivery and installation coordination;

·        and ongoing support when a payment failed or circumstances changed.

Each stage affected the others.

A change to a payment arrangement could influence when an order progressed.

A failed collection could require customer contact and a revised schedule.

Delivery teams needed accurate information about the order and its status.

Managers needed a reliable view of sales, expected income, outstanding balances and operational workloads.

The challenge was therefore not simply to integrate a payment gateway or build an online shop.

It was to create a connected commerce and operations platform around the way the business actually served its customers.

Looking Beyond the Checkout

Payment is often treated as the final step in an ecommerce journey.

For this client, it was part of a much longer relationship.

The system needed to understand the customer, the order, the agreement, the selected payment frequency, the amount already paid, the remaining balance and the next expected payment.

It also needed to connect that financial information to fulfilment and customer service.

This required a different approach from installing a standard ecommerce package and adding a payment plug-in.

We designed the platform around the underlying business entities and processes:

·        customers and addresses;

·        products, pricing and promotions;

·        orders and order items;

·        payment arrangements and transaction schedules;

·        individual transactions and allocations;

·        preparation and fulfilment statuses;

·        deliveries and service-team activity;

·        customer communications;

·        exceptions, issues and follow-up actions;

·        and operational and financial reporting.

By representing these as connected parts of one platform, the technology could support the complete customer and order lifecycle.

Making Flexible Payments Part of the Product

Flexible ways to pay were not an optional addition to the platform.

They were part of the client's core customer proposition.

The system therefore needed to manage different payment arrangements while keeping a clear relationship between the order, each transaction and the customer account.

Customers could choose from the payment options made available for their purchase.

The platform recorded successful and unsuccessful transactions and maintained the current position of each account.

Operational users could see:

·        the original order value;

·        the selected payment arrangement;

·        payments received;

·        the remaining balance;

·        the last successful collection;

·        the next payment date;

·        the current payment status;

·        and any action requiring attention.

This gave the business a single operational view rather than forcing staff to reconcile customer records, payment reports and order information manually.

It also meant that payment rules could reflect the realities of the business rather than being constrained by a generic checkout model.

Integrating Multiple Payment Providers

Payment technology changes over time.

Commercial terms change, providers introduce new capabilities, security requirements develop and previously suitable services may no longer meet the needs of the business.

A business-critical commerce platform therefore cannot assume that one payment integration will remain unchanged forever.

Over the course of the engagement, Irvine-David integrated the platform with multiple card-processing and bank-payment services.

This included support for one-off transactions, recurring card payments, tokenisation and bank-based collections.

Each provider exposed different APIs, authentication models, transaction states and error responses.

The challenge was to accommodate those differences while presenting a coherent internal process to the rest of the business.

The platform records the operational information needed to connect an external transaction with the correct customer, order and payment arrangement.

Provider responses are translated into meaningful business outcomes such as authorised, declined, pending, failed or cancelled.

That allows the wider system to respond appropriately without every operational workflow needing to understand the technical details of each payment service.

The payment provider can change. The business process remains understandable and controlled.

Supporting Payment-Provider Migration

Changing payment providers is considerably more difficult when a business manages recurring customer arrangements.

It is not simply a matter of replacing the provider used by a checkout page.

Existing customer arrangements, permissions, payment references, future transactions, histories and reconciliation processes all need to be considered.

The platform has evolved through several generations of payment technology.

Irvine-David supported those changes while preserving the underlying customer and operational history.

New integrations could be introduced alongside existing arrangements, allowing the business to move forward without treating every provider change as a replacement of the wider commerce platform.

Migration tools and scheduled services supported the controlled movement of relevant customer payment data.

The wider system retained the information required by sales, customer service, finance and delivery teams.

This reduced the operational risk normally associated with changing a service positioned at the centre of revenue collection.

It also gave the business greater freedom to select payment technology based on its current requirements rather than remaining tied indefinitely to an earlier technical decision.

Connecting Bank-Based Payments with Existing Workflows

As the client's payment strategy developed, the platform was extended to support bank-based payments alongside card-based collections.

This required more than presenting another payment option.

The system needed to manage customer authorisation, provider notifications, settlement information and changes in collection status.

Events received from the payment provider are connected back to the relevant customer account.

Successful setup can activate the appropriate collection arrangement.

A failed or cancelled authorisation can update the account and create an operational action for follow-up.

Settlement information can be reconciled against the corresponding customer balances.

This integration makes external payment activity part of the internal workflow.

Staff do not have to treat the payment-provider portal and the customer-management system as unrelated sources of information.

The platform connects the event to the customer context in which somebody can act upon it.

Managing Failed Payments and Customer Support

A successful payment is easy to automate.

The real operational challenge lies in what happens when a collection is unsuccessful.

A failed transaction may require another attempt, a conversation with the customer, a revised payment date or a different arrangement.

It may also affect an order or delivery already moving through the business.

The platform brings those exceptions into a structured process.

Failed collections can be identified and linked to the relevant customer and order.

Follow-up work can be prioritised, notes recorded and subsequent actions tracked.

Where appropriate, payments can be retried or taken manually through an authorised process.

Changes to balances or payment statuses create a visible history rather than silently altering the customer record.

This helps the business respond consistently while recognising that customer circumstances sometimes require human understanding and flexibility.

Technology manages the information and workflow.

Experienced staff manage the customer relationship.

Connecting Orders, Fulfilment and Delivery

Payment collection only creates value when the rest of the order can be fulfilled effectively.

The platform therefore extends beyond finance into the operational journey.

Orders contain the products, pricing, customer requirements and notes needed by downstream teams.

Statuses allow work to move through preparation, fulfilment and delivery stages.

Delivery teams can access the information required to plan and complete their work.

Issues can be recorded and followed through rather than disappearing into informal messages.

Because these activities share the same underlying customer and order data, teams have a more consistent picture of what has been agreed and what should happen next.

This reduces repeated data entry and avoids the gaps that appear when sales, payments and fulfilment are managed in separate applications.

It also provides management with a clearer view of work progressing through the business.

Supporting Sales and Service Teams

The customer journey was not confined to the checkout.

Sales and service teams also needed to work with customers, capture requirements and move enquiries towards an order.

Dedicated workflows help coordinate customer enquiries, sales activity and follow-up priorities.

Information captured during the sales process becomes part of the same customer record used by payment, service and fulfilment teams.

This creates a more joined-up experience for the customer.

They do not need to repeat the same information at each stage, and staff can understand the history of the relationship before making contact.

The platform also helps managers allocate work and understand activity across different teams.

Digitising Agreements and Customer Communications

Orders and payment arrangements require clear documentation.

The platform generates customer-specific order and payment documents using information already captured during the sales process.

Customers can review and accept those documents digitally, reducing delays and avoiding the need to reproduce the same details manually.

Receipts, statements and other communications can be generated from the transaction history held within the system.

This improves consistency between what was sold, what the customer agreed, what has been paid and what remains outstanding.

It also creates a more professional customer experience while giving the business a clearer record of important interactions.

Creating Operational Visibility

A connected platform creates information that individual systems cannot provide on their own.

Management can see activity across customers, orders, expected collections, failed payments, outstanding balances, fulfilment and delivery.

Dashboards and reports help teams identify what requires attention rather than relying on manually assembled spreadsheets or isolated provider reports.

This supports questions such as:

·        Which orders are ready to progress?

·        What income is expected over the coming period?

·        Which payments have failed or require intervention?

·        Which customer accounts have outstanding actions?

·        What work is moving through fulfilment and delivery?

·        Where are operational delays or exceptions emerging?

·        How are sales, collections and fulfilment performing?

Better visibility allows the organisation to manage by exception.

People can focus on the orders and customers that need attention while routine activity moves through a defined process.

Building a Platform, Not a Collection of Integrations

Payment integrations are sometimes treated as isolated technical projects.

For this client, their value comes from being connected to everything around them.

A payment relates to a customer arrangement.

That arrangement relates to an order.

The order relates to a customer and a fulfilment process.

An unsuccessful payment may create a service action.

A completed payment stage may allow the next operational stage to begin.

A provider migration must preserve the history required by the wider business.

The system was therefore designed as a business platform rather than a set of disconnected gateway integrations.

Shared customer, order and payment data supports multiple applications and teams.

Scheduled services automate routine processing.

Specialist integrations connect external payment events to internal workflows.

Reporting turns operational activity into management information.

This connected design is what allows the technology to support the complete commercial model.

Evolving Alongside the Business

The platform has continued to develop as the client's needs have changed.

New payment methods have been introduced.

Existing integrations have been replaced or modernised.

Payment workflows and business rules have become more sophisticated.

Customer documents, reporting and operational tools have been expanded.

Sales, fulfilment, service and delivery workflows have evolved around real-world experience.

This long-term development model has allowed the client to respond to changes without repeatedly replacing its core systems.

Instead, new capabilities have been incorporated into the platform while preserving the knowledge, data and processes the business already depends upon.

That continuity is particularly valuable in payments.

External providers will continue to change, but the organisation retains control of the customer journey and the operational model around them.

The Result

The platform provides the client with an end-to-end digital foundation for commerce, payments and fulfilment.

Customers benefit from flexible ways to pay, clear digital agreements and a more joined-up experience.

Operational teams work from shared customer, order and payment information rather than maintaining separate records.

Automated schedules and payment-provider integrations reduce repetitive administration.

Exceptions such as failed collections are surfaced for action rather than being lost in external reports.

Fulfilment and delivery activity remains connected to the commercial and financial context of each order.

The resulting benefits include:

·        more flexible payment options for customers;

·        support for recurring card and bank-based collections;

·        greater freedom to adopt and migrate between payment providers;

·        less manual reconciliation and repeated data entry;

·        faster identification of payment exceptions;

·        more consistent customer agreements and records;

·        clearer coordination across sales, service, fulfilment and delivery;

·        better operational and financial reporting;

·        fewer avoidable errors and hand-off gaps;

·        and a scalable platform capable of supporting continued business change.

The most important achievement is not any single payment integration or application.

It is the creation of a connected system in which the complete customer journey can be managed as one business process.

How Irvine-David Helped

Irvine-David designed and built the platform from the ground up, translating a complex operating model into practical software used across the business.

Our involvement has covered ecommerce, customer and order management, payment workflows, payment-provider integrations, tokenised and recurring collections, bank-based payments, digital documents, fulfilment, delivery, customer service, reporting and scheduled automation.

We have also provided the ongoing technical leadership needed to adapt the platform as payment services, operational requirements and commercial priorities have changed.

This combination of business understanding, payment integration expertise and long-term hands-on delivery is central to how we work.

The objective was never simply to build a checkout or connect a payment gateway.

It was to create technology capable of supporting the client's complete commercial model and continuing to evolve with the business.