Payments in the Order in Store

The Order in Store module can be integrated with various payment providers to facilitate in-store payments. This page will cover the different types of payments, the payment processing methods, and the necessary configurations for this purpose.

Payment Provider

Payment Types

Payment Processing

Split Payment

Payment Provider

Payment Types

Payment Processing

Split Payment

Stripe

  • Payment terminal

  • Immediate capture

  • Authorization & Capture

Supported

Adyen

  • Payment terminal

  • Pay by link

  • Immediate capture

  • Authorization & Capture

Supported

HiPay

  • Payment terminal

  • Pay by link

  • Immediate capture

Not Supported

Split Payments

During checkout in the Order in Store, customers have the option to split a payment into multiple payments. This functionality caters to group purchases and individuals who prefer using different payment methods for a single large purchase.

Configuring Your Site for Split Payments

Select Payment Providers Supporting Split Payments Only

To enable split payments, ensure that all payment methods used in the Order in Store support this feature. For instance, if a stock location accepts payments via Adyen and Stripe, split payments will be activated. However, if HiPay and Stripe are accepted at another stock location, split payment will not be active.

Adjust your order life cycle graph to handle refunds

In cases where a payment is abandoned before completion, partial invoices need to be refunded. To address this scenario, configure your order life cycle graph to trigger a refund when the order transitions to the "payment failed" state. This setup guarantees automatic fund refunds.

In The Order Workflow

  • Introduce a new state called "payment_failed" (or equivalent)

  • Include an action to send notifications of changing state to "payment_failed" upon order creation

  • Add a transition from pending state to "payment_failed" with actions such as:

    • Disabling notification of state change

    • Updating line item group states to "payment_failed"

    • Initiating a refund using create_payment_execution for the entire order

add a new state payment_failed (or equivalent but payment_failed is the standard one)
add a send_change_state_notification to change the state to payment_failed at order creation

 

 

In the line item group workflow

  • add a new state payment_failed (or equivalent but payment_failed is the standard one)

  • add a transition pending → payment_failed (no actions or conditions needed)

Â