Different ideal methods

Johnny vd Laar - November 20, 2008 - 12:46
Project:iDeal payment API
Component:Miscellaneous
Category:task
Priority:normal
Assigned:Unassigned
Status:active
Description

we are using ideal from neos solutions and ideal from docdata payments (before tripledeal). neos solutions is a division of Fortis (http://www.neossolution.com/section/NL/NL/) and it actually uses the ogone payment provider (http://www.ogone.com/). I think a lot of banks are using the Ogone/Neos implementation. But I also think even more suppliers exist for ideal and i'm not sure about the implementations of these frameworks. but i think most suppliers would provide us with enough documentation about how to build for their payment providers.

for docdata there is one problem. their testing server doesn't support ideal. their production server does support ideal.

so i think the best payment provider to start for would be neos/ogone as this would also mean we would have an implementation for fortis and abn amro. this module already implements an ogone payment provider for ubercart: http://drupal.org/project/uc_ogone

as a side node, when we use a payment provider. we usually use multiple payment methods from this provider (for example ideal and creditcard payments).

but tbh the current ideal system isn't an ideal platform to develop for ;)

 
 

Drupal is a registered trademark of Dries Buytaert.