Skip to content
Search Articles/

less than a minute read • Updated an hour ago

Ogone

Connect Foxy to Ogone for secure payments.

Features
  • Auth Only & Delayed Capture
  • Multi-Currency

Ogone connects Foxy to the legacy Ogone / Ingenico ePayments platform, using the credential model built around a PSPID, SHA-IN, and SHA-OUT. Worldline — which now owns this platform after acquiring Ingenico — ended vendor support for it on December 31, 2025. That date has already passed. Worldline's current recommendation for anyone on this legacy integration is to migrate to Worldline Direct's Hosted Checkout Page, which is exactly what Foxy's separate Worldline Hosted gateway connects to (see that article).

This article is written for merchants who are already connected to Ogone, not for anyone starting fresh. As of February 2026, Foxy recorded 0 active connections to this gateway type but 12,483 transactions (0.61% of processed volume) — meaning at least one existing merchant is still running real production traffic through it, even though the vendor considers the platform past its support window. Foxy has not built any newer integration path for this gateway — there is no fallback if Worldline enforces the cutoff. If you are that merchant, start your migration to Worldline Hosted now; don't wait for something to break first.

Setting up Ogone

Do not use this as a starting point for a new integration. It's kept here for merchants who need to review or troubleshoot an existing connection.

  1. 1

    In the Ogone/Ingenico back office, go to Configuration > Technical Information > Global security parameters and set the hash algorithm to SHA-512 (the platform's older default is SHA-1).

  2. 2

    In the Data and origin verification tab, set a SHA-IN pass phrase — long, with a mix of letters, numbers, and special characters.

  3. 3

    In the Transaction feedback tab, set a separate SHA-OUT pass phrase. Use a different value from SHA-IN.

  4. 4

    Configure the HTTP redirection and direct server-to-server request URLs in the back office to point at your Foxy store, per the platform's own setup documentation.

  5. 5

    In the Foxy administration at https://admin.foxy.io, go to Settings > Payments.

  6. 6

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

  7. 7

    Click Add payment method + and choose Ogone.

  8. 8

    Enter your PSPID in the PSPID field, your SHA-IN pass phrase in the SHA-IN field, and your SHA-OUT pass phrase in the SHA-OUT field.

  9. 9

    Click Create.

The panel is split into a Live setup block and a Test setup block carrying the same three fields (PSPID, SHA-IN, SHA-OUT).

Testing

Foxy provides shared test credentials for Ogone, so you can technically run test transactions without setting up your own sandbox account. Leave the Test setup fields as they are. Given that the vendor's own support window for this platform has closed, treat any test transaction on this gateway as informational rather than a reliable signal — there is no guarantee Worldline's legacy test infrastructure behind it will keep behaving the way it has historically.

Obtaining a test account

The wiki points to https://secure.ogone.com/ncol/test/new_account.asp for requesting a test account. That URL still loads (verified), but given that Worldline's own migration documentation describes the legacy integration methods living at secure.ogone.com as past their support end-date, we could not confirm whether it still issues working new test accounts. Confirm directly with Worldline before relying on it.

Test card numbers

Neither the wiki nor the pack provides Ogone-specific test card numbers. The wiki explicitly says to contact Ogone/Worldline directly for these. We did not invent any. If you need them, ask Worldline support, or check whatever test-card list they still maintain for the legacy platform.

Advanced features

The pack records no additional fields for this gateway beyond PSPID, SHA-IN, and SHA-OUT. It also records supports_auth_only: true (authorize-only transactions are supported) and supports_multi_currency: true.

Important notes and caveats

  • This platform is past its vendor support window. Worldline's own migration documentation states that legacy integration methods and endpoints under secure.ogone.com — the Hosted Payment Page, DirectLink, FlexCheckout, and e-Terminal/batch methods, all built on the same PSPID/SHA-IN/SHA-OUT credential model this Foxy gateway uses — "remain available until December 31st 2025." We verified this directly on Worldline's current documentation site. That date is in the past as of this writing.

  • Foxy has not built a newer integration path for this gateway. The Foxy integration is still active (is_deprecated: false) and still carries real transaction volume, but it is entirely the original PSPID/SHA-IN/SHA-OUT flow — no updated code path exists. That combination — a vendor platform past its stated support date, a live non-deprecated Foxy gateway, and no code-level fallback — means an existing merchant relying on this can plausibly keep working today, but has no guarantee Worldline won't cut it off without further notice, and no safety net on Foxy's side if it does.

  • Migration path: Worldline recommends moving to its Direct product using the Hosted Checkout Page integration method. Foxy's separate Worldline Hosted gateway is that same product — merchants should migrate their payment method to Worldline Hosted rather than staying on Ogone.

  • No subscription support, per the wiki. We could not independently verify this against the API pack (it records no subscription-support flag for any gateway type), so treat this as a wiki claim carried forward, not pack-confirmed.

Troubleshooting

If a live transaction fails with a message indicating you need backend access to see details, that's consistent with the account not being fully activated, or activation lapsing — contact Worldline support (not Ogone; Ogone as a standalone support channel no longer exists) to confirm your account's status on the legacy platform.

For declined transactions or unrecognized response codes, contact Worldline — they own the response code definitions for this platform.

If you're setting up anything new, stop and use Worldline Hosted instead of continuing here.

Need Help?

Did this article answer your questions? Need help with anything? Please click below to contact us.