Skip to main content
Worldpay is a global payment processor providing card acquiring and alternative payment methods across Europe, the Americas, and Asia-Pacific.

​
Processor Details

​
Integration Guide

1

Open Worldpay Merchant Admin Interface

Log in to the Worldpay Merchant Interface (MAI) and ensure your merchant code and API credentials are active.
2

Collect credentials

Obtain the following credentials from Worldpay:
  • Merchant Code
  • API Username
  • API Password
API credentials are separate from Merchant Interface login credentials.
3

Add integration in PayNext

In Dashboard → Integrations, click Add new integration → Worldpay → Connect
4

Enter credentials

  • Name: Label for this connection (e.g., “Worldpay EU”)
  • Merchant Code
  • API Username
  • API Password
  • Network Tokens: Enable if activated by Worldpay
5

Save

Click Connect to complete the integration
6

Add Worldpay Webhook sending

In Worldpay MAI navigate to “Integration” tab on the left, then click Merchant Channel
1
There configure Merchant Channels http protocol:
  • Active: yes
  • Content: xml
  • Address: Check this in PayNext CRM on integrations page
  • Method: POST
2
Then lower in Merchant Channel Events mark following columns in http row:
  • CAPTURED
  • SETTLED
  • SETTLED_BY_MERCHANT
  • VOIDED
  • REFUNDED
  • REFUNDED_BY_MERCHANT
  • REFUND_FAILED
  • REFUND_REVERSED

​
Metadata Mapping

Worldpay supports passing merchant-defined metadata in authorization requests. This allows you to control statement descriptors and attach additional context for reconciliation.
Descriptor customization must be enabled on your Worldpay account. Contact Worldpay support if fields are not reflected on statements.
Supported Fields: Example Usage:
Update Customer Metadata

​
FraudSight Device Data

Worldpay’s FraudSight scores a transaction using a device profile collected in the shopper’s browser. Collection runs on your checkout page and returns a session ID; PayNext forwards that ID on the authorization so Worldpay ties the profile to the transaction.
FraudSight must be enabled on your Worldpay merchant account. Contact Worldpay support to enable it and to confirm which device data collection script your account uses.
To pass a device session ID:
  1. Ask Worldpay to enable FraudSight on your merchant account
  2. Collect the device session ID in your checkout using Worldpay’s device data collection for web
  3. Store the ID in payment metadata under a key of your choice (e.g. wp_device_session)
  4. Map that key to deviceSession.sessionId — see Metadata Mapping
Create Payment
The session ID is read from payment metadata only, not from customer or subscription metadata. A device profile belongs to one checkout, so an ID stored on a customer would be replayed on later merchant-initiated charges and describe the wrong session.
Worldpay validates the session ID value and rejects the whole authorization with <error code="5"> when it is not acceptable — no authorization is attempted. Pass the ID exactly as the collection script returns it; do not add punctuation, markup, or your own prefixes. PayNext trims surrounding whitespace and omits the element when the mapped value is empty or longer than 128 characters, so a broken mapping drops the fraud signal instead of blocking the payment.
Verify the device session is sent: Check the authorized payment payload in the PayNext dashboard. The order should include:
If the element is absent, the mapping target does not match deviceSession.sessionId exactly (it is case-sensitive), the metadata key holds no value on that payment, or the value was dropped by the checks above.