Cannot initiate recurring payment

[monomelodies]

Calling checkout with the following data succesfully creates a new payment:

$data = [
'Amount' => (int)$plan->price,
'Currency' => 'EUR',
'Paymentmethod' => strtoupper($method),
'Issuer' => $provider,
'Country' => 'NL',
'Language' => 'NL',
'Description' => 'Recurring subscription',
'OrderID' => (string)$subscription->id,
'Reference' => (string)$subscription->id,
'CustomerID' => (string)$this->user->ID,
];

Using the same data to initiate a vault checkout raises the following error:

object(stdClass)#25 (1) { ["Message"]=> string(99) "Validation failed for one or more entities. See 'EntityValidationErrors' property for more details." }

I have no idea where I would find the EntityValidationErrors property to debug this further...

[tsygankov]

Hi monomelodies,

Looks like this is a model validation error on the gateway side. I will contact ICEPAY development team and ask them to add exception shielding.

["Message"]=> string(99)
It looks like one of the parameters is not valid. Probably ICEPAY Payment Gateway expects string parameter with maximum length of 99 chars, however for some reason the value that you are sending is invalid.

Can you please var_dump the $data array and check the values sent to the gateway?

[monomelodies]

Hi Tsygankov ;) Thanks for your reply. This is the EXACT data being posted: array(10) { ["Amount"]=> int(1900) ["Currency"]=> string(3) "EUR" ["Paymentmethod"]=> string(5) "IDEAL" ["Issuer"]=> string(7) "ABNAMRO" ["Country"]=> string(2) "NL" ["Language"]=> string(2) "NL" ["Description"]=> string(22) "Recurring subscription" ["OrderID"]=> string(3) "101" ["Reference"]=> string(3) "101" ["CustomerID"]=> string(1) "1" } (well, obviously the OrderID increments each time...) This same data works for a single payment, but not for a recurring one. AFAICT the docs state that for the initial vaultCheckout, a "normal" payment method must be used which is later "compatible" with the recurring ones (in this case, IDEAL with the intention of recurring with DDEBIT). Further info: if I pass in an orderID used previously in a test, I get the (somewhat expected) error that it is a duplicate. So strange enough, it initially accepts the data but rejects it later on based on some (undocumented?) deeper problem.

…

-marijn

On 05/02/2017 04:32 PM, tsygankov wrote: Hi monomelodies, Looks like this is a model validation error on the gateway side. I will contact ICEPAY development team and ask them to add exception shielding. |["Message"]=> string(99)| It looks like one of the parameters is not valid. Probably ICEPAY Payment Gateway expects string parameter with maximum length of 99 chars, however for some reason the value that you are sending is invalid. Can you please var_dump the $data array and check the values sent to the gateway? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAP4-gSRmGVw1Pz62_wHX5OtFwyF-KnYks5r1z6bgaJpZM4NN6tM>.

[monomelodies]

bump Any news on this? My client is getting a bit anxious, and we've been trying to get this sorted for a number of weeks now... ;)

Due to compliance reasons this product, Recurring Billing, is upon request only.

Hi Marijn, A look at the values you are posting shows a field CustomerID. However, for a Vault Checkout you should pass a field named ConsumerID. Can you check if this explains your problem? If not, I can do more checks on monday. Regards, Michiel Op 4 mei 2017 om 12:59 heeft Marijn Ophorst <notifications@github.com<mailto:notifications@github.com>> het volgende geschreven: bump Any news on this? My client is getting a bit anxious, and we've been trying to get this sorted for a number of weeks now... ;) — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#3 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AMIzzWoLyG9HARfSOYixxWKGm0cfDl-2ks5r2a93gaJpZM4NN6tM>. Disclaimer: Op al onze rechtsbetrekkingen zijn de Algemene Voorwaarden ICEPAY van toepassing. Deze voorwaarden bevatten een aansprakelijkheidsbeperking, zijn gedeponeerd bij de Kamer van Koophandel Haaglanden onder nummer 27348492 en worden op verzoek toegezonden. Toepasselijkheid van eventuele inkoop- of andere voorwaarden van opdrachtgever dan wel van derden wordt dan ook uitdrukkelijk van de hand gewezen door ICEPAY. Dutch law applies to the agreement between parties. The General Conditions ICEPAY apply to all proposals and deliveries made by ICEPAY. These conditions include a limitation on liability, are filed at the Chamber of Commerce in Haaglanden under number 27348492 and will be sent upon request. The applicability of purchase conditions or any other conditions from customer or from third parties is, then, expressly rejected by ICEPAY.

[monomelodies]

Never mind, turns out the issue is that recurring payments weren't enabled for him. I tried consumer instead of customer too btw, same result. Docs are ambiguous and should be fixed (as should the error - sth like an http/403 would be more logical...)

…

On 5 May 2017, at 18:04, Icepay B.V. ***@***.***> wrote: Hi Marijn, A look at the values you are posting shows a field CustomerID. However, for a Vault Checkout you should pass a field named ConsumerID. Can you check if this explains your problem? If not, I can do more checks on monday. Regards, Michiel Op 4 mei 2017 om 12:59 heeft Marijn Ophorst ***@***.******@***.***>> het volgende geschreven: bump Any news on this? My client is getting a bit anxious, and we've been trying to get this sorted for a number of weeks now... ;) — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#3 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AMIzzWoLyG9HARfSOYixxWKGm0cfDl-2ks5r2a93gaJpZM4NN6tM>. Disclaimer: Op al onze rechtsbetrekkingen zijn de Algemene Voorwaarden ICEPAY van toepassing. Deze voorwaarden bevatten een aansprakelijkheidsbeperking, zijn gedeponeerd bij de Kamer van Koophandel Haaglanden onder nummer 27348492 en worden op verzoek toegezonden. Toepasselijkheid van eventuele inkoop- of andere voorwaarden van opdrachtgever dan wel van derden wordt dan ook uitdrukkelijk van de hand gewezen door ICEPAY. Dutch law applies to the agreement between parties. The General Conditions ICEPAY apply to all proposals and deliveries made by ICEPAY. These conditions include a limitation on liability, are filed at the Chamber of Commerce in Haaglanden under number 27348492 and will be sent upon request. The applicability of purchase conditions or any other conditions from customer or from third parties is, then, expressly rejected by ICEPAY. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.