Pay.

Pay. payments for Medusa V2

Get access to 50+ payment options for online and in-store payments.

Getting Started

Don’t have an account with Pay. yet? Register now!

[!CAUTION] If you have subscribers listening to the order.placed event, update them to listen to the payment.captured event instead. See below.

[!WARNING] This plugin creates orders in Medusa immediately, even if the payment has not yet been captured. If a payment expires, the associated order will be automatically canceled.

This change in flow is required to support asynchronous payment methods (e.g., SprayPay), where payment confirmation can take hours depending on customer input.

Table of Contents

• Demo store
• Pay. Payment Methods
• Features
• Prerequisites
• Installation
• Configuration
  • Configuration Options
  • Environment Variables
• Usage
• Supported Payment Methods
• Client-Side Integration
  • Duplicate cart endpoint
  • Adding payment method icons
• Extending the Plugin
• Medusa v1 Support

Demo store

Visit the demo store here: https://pay-demo.webbers.com

Pay. payment methods

Card payment methods

• Mastercard
• VISA
• American Express
• Carte Bancaire
• Maestro
• PostePay
• DanKort
• Nexi
• Visa Mastercard

Digital wallets

• Apple Pay
• Google Pay

Afterpay methods / Buy now pay later

• iDEAL IN3
• Billink
• SprayPay
• Riverty
• Mondu
• AlmaPAY
• Klarna

Other

• PayPal

Recurring payments

• SEPA Direct Debit
• Card-on-file / recurring card payments (tokenisation) [Coming soon]

Region specific payment methods

InStore / SoftPOS payments

Would you like to integrate Pay. (Soft)P0S? Get in touch!

Features

• Easily Extendable: The modular architecture makes it easy to add support for additional Pay payment methods.
• Webhook Support: Full support for Pay webhooks for real-time payment status updates.
• Automatic Capture: Configurable automatic capture of payments.

Prerequisites

• Medusa server v2.20.1 or later
• Node.js v20 or later
• A Pay account and token & secret with payment methods enabled.

Installation

Configuration

Add the provider to the @medusajs/payment module in your medusa-config.ts file & add it as plugin:

Configuration Options

[!NOTE] You can get the API token & secret from your Pay dashboard: click Settings > Click sales channel > Copy api tokens

Environment Variables

Create or update your .env file with the following variables:

Usage

Once installed and configured, the Pay payment methods will be available in your Medusa admin. To enable them, log in to you Medusa Admin, browse to Settings > Regions, add or edit a region and select the desired Pay providers from the dropdown.

Make sure that the selected payment methods are enabled in your Pay origanization settings as well.

Testing direct debits locally

Pay.'s test environment does not process SEPA direct debits. With testMode enabled the plugin therefore does not create a mandate at Pay. when a direct debit order is placed. It stores a simulated mandate on the payment session instead (code TEST-<payment session id>, logged as Pay. direct debit test mode: storing simulated mandate ...), and the collection flow can be driven by posting the exchanges Pay. would normally send to the webhook route yourself. Exchanges for a simulated mandate are not re-fetched from Pay., the body is taken as the direct debit state. This only happens while testMode is on and only for mandates that were created in test mode.

Other legacy actions (incassopending, incassosend) and an explicit status: {"code": 106} (failed) or declined: true work the same way. Add "reference": "<order display id>" to the body when the order can not be resolved from the mandate code. The webhook route processes exchanges asynchronously (5 seconds by default), so give the server a moment before checking the order. The payment link opens the regular Pay. hosted checkout, so the outstanding amount can be paid with any test payment method.

Reversed payments in the admin

When a chargeback or storno reverses a captured payment, the plugin refunds the payment in Medusa (without contacting Pay.), books the amount as outstanding again and opens a new payment collection, so the order offers "Copy payment link" and "Mark as paid". Medusa's own payment status can only call that "Refunded", so the plugin adds a "Payment reversed, action required" banner on top of the order page that names the cause (chargeback, storno, failed collection), the amount that went back to the customer and what is still outstanding.

Simulator widget in the admin

The same exchanges can be triggered from the order detail page. Switch on SEPA testing in Settings > Pay (off by default, meant for staging servers) and a "Pay. direct debit simulator" panel appears in the sidebar of orders that hold a simulated mandate, with a button per exchange (pending, sent, collected, storno, failed, declined). The exchanges are processed synchronously, so the order refreshes right away. The switch is stored in the store's metadata (pay_sepa_testing), so it applies to every admin user of that server. The panel is backed by GET /admin/pay/orders/:id/direct-debit and POST /admin/pay/orders/:id/direct-debit/exchange ({"action": "storno"}), which only work while the switch and testMode are on; the switch itself is read and written through GET/POST /admin/pay/settings ({"sepaTesting": true}).

Supported Payment Methods

The plugin currently supports the following Pay payment methods:

Client-Side Integration

To integrate with your storefront, you'll need to implement the payment flow according to Pay's and Medusa's documentation. Here's a basic example:

1. Create a payment session in your checkout flow
2. Redirect the customer to the Pay payment page
3. Handle the webhook notifications to update the payment status

Example integration using the Medusa Next.js Starter:

https://github.com/user-attachments/assets/742ee261-5e41-4e33-9a72-faf1a424fc52

Duplicate cart endpoint

[!TIP] Use the duplicate cart endpoint in your storefront

When a customer cancels a payment or returns to the storefront without completing the Pay. checkout, a new duplicate cart should automatically be created. This allows the customer to easily start a new transaction without losing the items they had selected.

API Route: GET /store/carts/:id/duplicate

Alter your storefront retrieve cart function(s) and check if the returned cart.completed_at value is set. If so request a new cart with the duplicate cart endpoint and update cart id in cookies accordingly.

The duplicate cart endpoint is idempotent, so it can be called multiple times with the same cart id.

Adding payment method icons

1. Download the latest payment images from here: https://github.com/paynl/payment-images
2. Add these to your storefront public assets
3. In your checkout, create the mapping from the provider id to the icon.
4. You can also utilize the exported payPaymentMethods from this plugin to find the corresponding ID.
5. I.e. const paymentMethodData = payPaymentMethods.find(method => `pp_${method.value}_pay` === provider_id)

Extending the Plugin

To add one of the missing Pay payment methods, create a new service in src/providers/Pay/services that extends the PayBase class:

Make sure to replace new method with the actual Pay payment method ID.

Export your new service from src/providers/Pay/services/index.ts. Then add your new service to the list of services in src/providers/Pay/index.ts.

We will be working on providing all the available Pay. options in the near future.

Medusa v1 Support

Searching for support for Medusa v1, we have a legacy plugin available. Get in touch