Ingenico ePayments (formerly Ogone) Gateway Guide

close

Services and Compatibility

Payment Gateway Company Name:
Ingenico ePayments (formerly Ogone)
Services that work with Spreedly:
  • Ingenico ePayments (formerly Ogone)
Supported operations:
Purchase, Authorize, Capture, Refund, Void, Verify
Does Spreedly support 3D Secure with this gateway?
Yes
Regions:
Europe

Authentication and Security

Specific names for credentials:
default mode:
Pspid, Signature Strength, Userid, Password, Signature
no_signature mode:
Pspid, Userid, Password

Onboarding Merchants in:

Additional Notes

Default Mode

To add an Ingenico ePayments (formerly Ogone) gateway:


curl https://core.spreedly.com/v1/gateways.xml \
  -u 'Ll6fAtoVSTyVMlJEmtpoJV8S:RKOCG5D8D3fZxDSg504D0IxU2XD4Io5VXmyzdCtTivHFTTSy' \
  -H 'Content-Type: application/xml' \
  -d '<gateway>
        <gateway_type>ogone</gateway_type>
        <pspid>psp</pspid>
        <userid>user</userid>
        <password>password</password>
        <signature>sig</signature>
        <signature_strength>sha512</signature_strength>
      </gateway>'

The signature_strength can be either sha256 or sha512, and will have to match the strength set in the Ogone backend.


<gateway>
  <token>WRicUGR5qYxABJLSknFHv3crdNy</token>
  <gateway_type>ogone</gateway_type>
  <name>Ingenico ePayments (formerly Ogone)</name>
  <description nil="true"/>
  <pspid>psp</pspid>
  <userid>user</userid>
  <signature_strength>sha512</signature_strength>
  <characteristics>
    <supports_purchase type="boolean">true</supports_purchase>
    <supports_authorize type="boolean">true</supports_authorize>
    <supports_capture type="boolean">true</supports_capture>
    <supports_credit type="boolean">true</supports_credit>
    <supports_general_credit type="boolean">false</supports_general_credit>
    <supports_void type="boolean">true</supports_void>
    <supports_verify type="boolean">true</supports_verify>
    <supports_reference_purchase type="boolean">false</supports_reference_purchase>
    <supports_purchase_via_preauthorization type="boolean">false</supports_purchase_via_preauthorization>
    <supports_offsite_purchase type="boolean">false</supports_offsite_purchase>
    <supports_offsite_authorize type="boolean">false</supports_offsite_authorize>
    <supports_3dsecure_purchase type="boolean">true</supports_3dsecure_purchase>
    <supports_3dsecure_authorize type="boolean">true</supports_3dsecure_authorize>
    <supports_store type="boolean">false</supports_store>
    <supports_remove type="boolean">false</supports_remove>
    <supports_fraud_review type="boolean">false</supports_fraud_review>
    <supports_disburse type="boolean">false</supports_disburse>
  </characteristics>
  <credentials>
    <credential>
      <name>pspid</name>
      <value>psp</value>
    </credential>
    <credential>
      <name>userid</name>
      <value>user</value>
    </credential>
    <credential>
      <name>signature_strength</name>
      <value>sha512</value>
    </credential>
  </credentials>
  <gateway_specific_fields>
  </gateway_specific_fields>
  <payment_methods>
    <payment_method>credit_card</payment_method>
  </payment_methods>
  <state>retained</state>
  <redacted type="boolean">false</redacted>
  <created_at type="dateTime">2016-08-11T17:15:23Z</created_at>
  <updated_at type="dateTime">2016-08-11T17:15:23Z</updated_at>
  <mode>default</mode>
</gateway>

No Signature Mode

Legacy Ogone accounts may not require or use a signature; for these you can specify the no_signature mode:


curl https://core.spreedly.com/v1/gateways.xml \
  -u 'Ll6fAtoVSTyVMlJEmtpoJV8S:RKOCG5D8D3fZxDSg504D0IxU2XD4Io5VXmyzdCtTivHFTTSy' \
  -H 'Content-Type: application/xml' \
  -d '<gateway>
        <gateway_type>ogone</gateway_type>
        <mode>no_signature</mode>
        <pspid>psp</pspid>
        <userid>user</userid>
        <password>password</password>
      </gateway>'

<gateway>
  <token>QzsLIwctnfMaAxtgi3uLWeVN4yt</token>
  <gateway_type>ogone</gateway_type>
  <name>Ingenico ePayments (formerly Ogone)</name>
  <description nil="true"/>
  <pspid>psp</pspid>
  <userid>user</userid>
  <characteristics>
    <supports_purchase type="boolean">true</supports_purchase>
    <supports_authorize type="boolean">true</supports_authorize>
    <supports_capture type="boolean">true</supports_capture>
    <supports_credit type="boolean">true</supports_credit>
    <supports_general_credit type="boolean">false</supports_general_credit>
    <supports_void type="boolean">true</supports_void>
    <supports_verify type="boolean">true</supports_verify>
    <supports_reference_purchase type="boolean">false</supports_reference_purchase>
    <supports_purchase_via_preauthorization type="boolean">false</supports_purchase_via_preauthorization>
    <supports_offsite_purchase type="boolean">false</supports_offsite_purchase>
    <supports_offsite_authorize type="boolean">false</supports_offsite_authorize>
    <supports_3dsecure_purchase type="boolean">true</supports_3dsecure_purchase>
    <supports_3dsecure_authorize type="boolean">true</supports_3dsecure_authorize>
    <supports_store type="boolean">false</supports_store>
    <supports_remove type="boolean">false</supports_remove>
    <supports_fraud_review type="boolean">false</supports_fraud_review>
    <supports_disburse type="boolean">false</supports_disburse>
  </characteristics>
  <credentials>
    <credential>
      <name>pspid</name>
      <value>psp</value>
    </credential>
    <credential>
      <name>userid</name>
      <value>user</value>
    </credential>
  </credentials>
  <gateway_specific_fields>
  </gateway_specific_fields>
  <payment_methods>
    <payment_method>credit_card</payment_method>
  </payment_methods>
  <state>retained</state>
  <redacted type="boolean">false</redacted>
  <created_at type="dateTime">2016-08-11T17:15:23Z</created_at>
  <updated_at type="dateTime">2016-08-11T17:15:23Z</updated_at>
  <mode>no_signature</mode>
</gateway>

Configure for 3D-Secure

If you’re going to be using 3D-secure, there are extra configuration steps that must be completed. First, note that 3D-secure is incompatible with no_signature mode.

Second, it’s important to note that if this isn’t configured correctly, you aren’t guaranteed to get final/complete status for all transactions, so customers could be charged without your system getting updated with that fact. To verify, you need to do a production 3D-secure transaction and ensure you get a redirect and callback from Spreedly indicating the transaction has completed.

Third, you need to make 4 configuration changes in the Ogone backend under “Configuration” > “Technical information” > “Transaction feedback”:

  1. “I would like to receive transaction feedback parameters on the redirection URLs” needs to be checked.
  2. “Direct HTTP server-to-server request” needs to be set to “Online but switch to a deferred request when the online requests fail”.
  3. Under “Direct HTTP server-to-server request” both of the fields under “URL of the merchant’s post-payment page” need to be set to https://core.spreedly.com/transaction/<PARAMVAR>/callback.
  4. Under “Direct HTTP server-to-server request” the “Request method” needs to be set to “POST”.

The defaults for the rest of the fields should be fine. The above changes are highlighted on this image:

Ogone Transaction Feedback Configuration

If you’d like to request any gateway_specific_fields or gateway_specific_response_fields, please email support@spreedly.com with your request and the gateway documentation for the fields of interest.