Payment service providers

Payment providers (and known limitiations) currently supported by WebHare

Riverty (formerly Afterpay)

• Only B2C payments for NL is implemented
• Requires passing a lot more data (IP, billing address, customer information to StartPayment
• Orderids are max. 36 characters, min. 2 characters. Only A-Z,a-z,0-9,_ and - are allowed
• Requires you to have the user accept Afterpay's terms and conditions. See https://mip.afterpay.nl/en/direct-api-integration/ for link to their terms and ensure your payment method takes care of this
• Order using the email address rejection@afterpay.nl to test Afterpay rejection

More information: Afterpay homepage

External

The external PSP is used to set up payments that are resolved outside of WebHare.

iDEAL

The iDEAL provider directly links to iDEAL checkouts. If you're offering other payment methods than iDEAL, you would probably use a more generic payment provider

https://www.ideal-checkout.nl/

Ingenico

Formerly known as Ogone

Important settings:

• Algemene beveiligingsparameters

  • Hash-algorithme: SHA1

• Verificatie data en herkomst

  • SHA1-IN: instellen & noteren
  • SHA1 HASH ook voor Directlink instellen en noteren

• Transactiefeedback

  • SHA1-OUT: instellen & noteren
  • Ik wil de feedbackparameters van de transacties op de redirectie-URL's ontvangen.: JA
  • Je wil ook achteraf bevestigingen aanzetten, zodat je een notificatie krijgt van betalingen als men zelf het betaalproces afbreekt.

Then create an API user to allow verification of transactions

• Configuratie > Gebruikers

  • Nieuwe gebruiker
  • Profiel Admin
  • "API gebruiker" vinkje aanzetten

Ingenico transactions work by redirecting the user to a payment form instead of pre-announcing the transactions to the gateway. If the user doesn't complete the redirect no trace of the transaction will be there at Ingenico. Because of this, WebHare cannot tell the difference between the user still being en-route to the transaction page at Ingenico or having permantently abanonded the transaction and uses the configurable 'Expire after' timeout to decide when to consider pending transactions failed

Mollie

We implement V2 of the Mollie API.

Mollie payments may fail if you're behind a firewall. When developing you can disable 'webhooks' in the payment settings to prevent Mollie from trying to contact your server

Multisafepay

Sisow

Sisow support is limited to payment only (ie, no Afterpay or Klarna, which seem to require a deeper API integration here)

Test

The test payment provider allows you to use a safe 'loopback' payment method when developing new integrations with the payment API. You should always ensure this provider works before connecting different providers to your application.

Be careful about enabling the Test provider on production systems as payments made through the Test provider may appear to be actually completed payments to your application.

Useful test scenarios:

• Place an order with 'fraud' somewhere in your email address to trigger an error in StartPayment.
• Place an order with 'throw' somewhere in your email address to trigger a THROW in StartPayment.
• Place an order with 'fraud' somewhere in the last name to fail a payment - it will go through the payment pages but still be rejected and provide a 'htmlstatusforuser' to show on the payment page