Paymetric (Worldpay B2C)

What this integration actually connects to

The Foxy panel asks for an XiPay User and an XiPay Password, and that tells you what is on the other end.

XiPay — usually XiPay On-Demand — is Paymetric's own product name for its hosted payment-processing service. It is the component that takes an authorization or capture request, routes it to your acquirer, and returns the result to whatever system asked. It is processor-neutral: XiPay sits between you and your acquiring bank rather than being the acquirer itself. Foxy's integration is fully built out against this API — every stage of a transaction's life (authorize, sale, capture, void, refund, and a card-verification flow) is implemented, with the XiPay SOAP endpoints (xipayapi.paymetric.com) doing the work.

Paymetric's other well-known component is XiIntercept, its tokenization technology, which captures card data and substitutes a token so the raw card number never reaches the merchant's own systems. The Merchant GUID and Shared Key fields in the Foxy panel are Paymetric's merchant-identity and request-signing credentials for a separate tokenization endpoint (xiecomm.paymetric.com) in this family of APIs, and Foxy's checkout also loads a Paymetric-hosted script from that same host to tokenize card data client-side.

The practical consequence for you: this integration talks to your Paymetric account, configured by Paymetric for your acquirer and your card types. Almost everything that determines how it behaves lives on the Paymetric side, not in Foxy.

Setting up Paymetrics(Worldpay B2C)

You need an existing Paymetric account. There is no self-serve signup — contact your Worldpay or Paymetric representative to have an account provisioned and to be issued the credentials below.

Foxy's panel asks for five credential values plus two settings. All five values come from Paymetric:

• Merchant GUID — your merchant identifier in Paymetric's APIs.

• Merchant ID — your merchant ID. (This field is masked in the Foxy admin, with a reveal icon, even though the Merchant GUID above it is not.)

• Shared Key — the key used to sign requests to Paymetric. Masked.

• XiPay User — the username for your XiPay account.

• XiPay Password — the password for that XiPay user.

Then, in the Foxy administration at https://admin.foxy.io:

1. 1

   Go to Settings > Payments.

2. 2

   Select the payment method set you want to use. If you only have one, it will be the Default Payment Method Set.

3. 3

   Click Add payment method + and choose Paymetrics(Worldpay B2C).

4. 4

   Under Live setup, enter the five values above in the order they appear: Merchant GUID, Merchant ID, Shared Key, XiPay User, XiPay Password.

5. 5

   Set Card verification. It defaults to Off, and the Foxy admin's own help text on this field says "Will never verify payment methods. Not recommended." Do not leave it on the default unless you have a specific reason to.

6. 6

   If you want to authorize at checkout and capture the funds later rather than at the time of sale, switch on Authorize only (no capture). It is off by default.

7. 7

   Click Create to save the payment method.

The panel is split into a Live setup block and a Test setup block carrying the same field list. Fill in your own credentials under Live setup. (The Live heading reads "Live setup (inactive)" while the payment method set has Use live credentials switched off — that reflects the current state of the set, not a different set of fields.)

Foxy does not publish a step-by-step walkthrough of where each of these five values appears inside the Paymetric portal, because Paymetric's merchant documentation is not public. If you cannot locate one of them, ask your Paymetric representative for the Merchant GUID, Merchant ID, Shared Key and XiPay credentials for your account by those names — they are Paymetric's own terms and your representative will recognise them.

Testing

Foxy provides shared test credentials for Paymetric, so you can run test transactions without arranging your own sandbox.

Those shared credentials only exercise the integration itself. If you need to test against your own Paymetric account configuration — your own acquirer routing, your own enabled card types, your own tokenization setup — ask your Paymetric representative for a test account and enter its credentials in the Test setup fields.

Obtaining a test account

Contact your Worldpay or Paymetric representative. Paymetric does not offer public sandbox self-signup.

Test card numbers

Foxy does not have a published test card list for this gateway. Request the current test card numbers from your Paymetric representative — which cards work in test depends on how your account is configured.

Advanced features

• Authorize only. Supported, via the Authorize only (no capture) toggle.

• Multiple currencies. The gateway supports multi-currency processing, subject to what is enabled on your Paymetric account.

• Card verification. Supported, via the Card verification dropdown.

Troubleshooting

If a transaction is declined or returns a response code you do not recognise, contact Worldpay or Paymetric. They own the response code definitions for this platform and can see transaction detail that Foxy cannot.

If authentication fails immediately after setup, re-check that the Merchant GUID and the Merchant ID have not been entered into each other's boxes — they are different values with confusingly similar names, and Merchant ID being masked while Merchant GUID is not makes a swap harder to spot.