Novalnet SEPA provider in ai-payments seems outdated – update to current Omnipay gateway?
Forum rules
Always add your Aimeos and PHP version as well as your environment (Linux/Mac/Win)
Spam and unrelated posts will be removed immediately!
Always add your Aimeos and PHP version as well as your environment (Linux/Mac/Win)
Spam and unrelated posts will be removed immediately!
Novalnet SEPA provider in ai-payments seems outdated – update to current Omnipay gateway?
Hello Aimeos team,
I'm currently trying to use the built-in Novalnet SEPA payment provider from the aimeos/ai-payments package in an Aimeos 24.4 installation.
Unfortunately, it seems that the implementation is based on an older Novalnet Omnipay gateway.
The problem starts in OmniPay.php, where the provider is instantiated via:
The old package fruitcake/omnipay-novalnet (formerly arubia/omnipay-novalnet) still provides that namespace, but it depends on omnipay/common 2.5, which is incompatible with current Aimeos installations using Omnipay 3.x.
The current official Novalnet package is:
From what I can see, the current NovalnetSepa provider in ai-payments still uses the old request format (iban, bic, bankaccount_holder, ...), so it appears to target the legacy gateway.
My questions are:
Are there any plans to update the built-in Novalnet SEPA provider to support the current official novalnet/omnipay package?
Would such an update be accepted as a contribution or is the provider considered deprecated?
If not, would you recommend writing a custom payment provider for the new Novalnet gateway instead?
If this is something that could be implemented by the Aimeos team, would paid development be an option?
I would appreciate your recommendation before investing time in writing a completely new payment provider.
Thank you very much!
Best regards,
Claude
I'm currently trying to use the built-in Novalnet SEPA payment provider from the aimeos/ai-payments package in an Aimeos 24.4 installation.
Unfortunately, it seems that the implementation is based on an older Novalnet Omnipay gateway.
The problem starts in OmniPay.php, where the provider is instantiated via:
With the configuration$this->provider = OPay::create($this->getValue('type'));
Omnipay tries to instantiatetype = Novalnet
which no longer exists.\Omnipay\Novalnet\Gateway
The old package fruitcake/omnipay-novalnet (formerly arubia/omnipay-novalnet) still provides that namespace, but it depends on omnipay/common 2.5, which is incompatible with current Aimeos installations using Omnipay 3.x.
The current official Novalnet package is:
which providesnovalnet/omnipay
and also uses a different API and request structure (Payment Access Key, API Signature, Tariff ID, etc.).\Novalnet\Omnipay\Gateway
From what I can see, the current NovalnetSepa provider in ai-payments still uses the old request format (iban, bic, bankaccount_holder, ...), so it appears to target the legacy gateway.
My questions are:
Are there any plans to update the built-in Novalnet SEPA provider to support the current official novalnet/omnipay package?
Would such an update be accepted as a contribution or is the provider considered deprecated?
If not, would you recommend writing a custom payment provider for the new Novalnet gateway instead?
If this is something that could be implemented by the Aimeos team, would paid development be an option?
I would appreciate your recommendation before investing time in writing a completely new payment provider.
Thank you very much!
Best regards,
Claude
Re: Novalnet SEPA provider in ai-payments seems outdated – update to current Omnipay gateway?
If you can provide an updated integration for the Novalnet SEPA provider, we are more than happy to merge it into the aimeos/ai-payments extensions 
For paid development, ask the Aimeos company: https://aimeos.com/aimeos-gmbh/contact
For paid development, ask the Aimeos company: https://aimeos.com/aimeos-gmbh/contact
Professional support and custom implementation are available at Aimeos.com
If you like Aimeos,
give us a star
If you like Aimeos,