Selected work English content preview

Fintech / Payment engineering

4Square Payments

Payment routingthat fits the business.

4Square can route payments to different acquirers using configurable conditions and templates. We built that flexibility alongside 3DS authentication, an animated checkout journey and the tools merchants need to follow payments and payouts.

Discuss your payment platform

Drupal 10
PHP
Drupal Commerce
ECA
BPMN
JWT
Custom integrations

Configurable routingConditions + acquirer templates

Choose the conditions for each payment route

4Square can configure which acquirer receives a payment and reuse templates for each provider, while shoppers follow the same checkout journey.

Auto play01 / 01

Inside the project

Payment engineering for the whole purchase.

4Square needs control over how it routes payments while customers need a purchase they can follow. ViaLogos built configurable acquirer routing and 3DS handling for its points checkout. Shoppers see progress through payment and points delivery, including an explanation if the store is still awaiting an update. Merchants and operations staff can then review transactions, investigate discrepancies and understand payouts.

Project: 4Square Payments
Scope: Payment routing engine, 3DS, customer journeys, ERP, merchant dashboards and reconciliation

01 / The challenge

Bank verification can interrupt the purchase.

A shopper may leave checkout to verify their identity with the bank, then return expecting to finish the same purchase. If they revisit a completed order, checkout must recognise that they have already paid. Merchants also need to distinguish a failed payment from a successful payment whose order update has been delayed.

02 / The approach

Help customers finish and merchants follow through.

We built the bank return into the purchase journey so customers can continue after verification. Checkout recognises completed payments when an order is revisited. If the merchant's order has not caught up, the customer sees a pending explanation and an order reference. Operations staff can investigate the mismatch and resend the missed update through the ERP.

Using the application

What people can do.

Choose how payments reach acquirers

4Square can set the conditions that send a payment to a particular acquirer. Reusable templates accommodate each provider's requirements, so the team can change routing while customers continue through the same checkout.

Continue the purchase after 3DS verification

We built 3DS into checkout so shoppers can answer a bank challenge and return to finish paying. The journey also handles checks completed in the background, when the bank does not ask the shopper to take an extra step.

Show customers where their purchase stands

The journey uses animated progress cards, a rising points balance and a completion sequence to explain what is happening. If the store is still awaiting an update, customers get an explanation and an order reference, with the choice to wait or return to the store.

Follow an order through checkout and back to the store

Operations staff can follow the merchant's order, payment and any refund through the ERP. We made the ERP coordinate checkout and the merchant's updates, giving staff a way to investigate the purchase across those steps.

Understand transactions and payouts

Merchants can review who paid, the payment status and the associated financial activity. Fees, reserves and payout details help them understand which funds are available and what still needs attention.

Investigate an order that still looks unpaid

Staff can find a successful payment whose merchant order has not updated, compare the two and resend the missing notification. They can distinguish resolved transactions from those being retried or needing review.

Under the surface

The stack.

Drupal 10
PHP
Drupal Commerce
ECA
BPMN
JWT
Custom integrations

A closer look

See the different sides.

Concept illustrations show the payment journey and merchant operations. Photographs are stock imagery. These visuals do not show 4Square's private interfaces.

01 / Routing
4Square can configure which acquirer receives a payment and reuse templates for each provider, while shoppers follow the same checkout journey.
Concept illustration

02 / 3DS
Customers can verify their identity with the bank and return to finish their purchase. We built 3DS handling for frictionless checks and customer challenges.
Concept / Stock photography

03 / Journey
Animated progress carries customers through payment, points and merchant notification. A delayed merchant update gets its own explanation and order reference.
Journey illustration

04 / ERP
Merchants can review transactions and payout information. Operations staff use the ERP to follow orders through checkout, refunds and merchant updates.
Concept / Stock photography

05 / Reconcile
Staff can investigate why a paid order still looks unpaid to the merchant, resend a missed update and follow cases that still need attention.
Concept illustration

Phone photograph: Mikhail Nilov / Pexels · Merchant photograph: Kampus Production / Pexels · Pexels License

Your next project

What should your payment platform make possible?

Tell us where your current checkout or payment operations hold you back. We can work through the routing, customer experience and systems behind it with you.

Discuss your payment platform Visit 4Square Online consultation with the Via Logos team.