Discussions

Hi, In the documentation page for Prestashop, there is [this marketplace addon](https://addons.prestashop.com/en/payment/22827-satispay.html) linked. However, I found [this github project](https://github.com/satispay/prestashop-plugin) that seems to refer to the same plugin, even the same version. What are the differences (if any) between the two?

Hi, i'm trying use satispay staging API, i followed the guides and i create this CURL curl --location '<https://staging.authservices.satispay.com/g_business/v1/payments'> --header 'content-type: application/json' --header 'host: staging.authservices.satispay.com' --header 'date: Wed, 10 Jul 2024 13:53:39 GMT' --header 'digest: SHA-256=jWjmI6cdwHPUs3tNU1lXxaKxar4Kee+elPnr1dj2Pqg=' --header 'Authorization: Signature keyId="p3gko1cpv4ffl747u8er772jn4uk1qktr8o5k485fd09gff6ngoacp5eql6cd1fbfdn0kvkbli5maso7io5up8pevb3a12qhm4bn38mjgku254tglkt516rfn4kfj8rluc7l3f1ig2pj11u5kpc0mc1k2qp61llvg7q78ljn2q58k8e5m3ot96e3ftd9mllgghpljds8", algorithm="rsa-sha256", headers="(request-target) host date digest", signature="ixS7dKlEWigZ97LF3To6GbcQUgFWIFNSuSpwEcRqEVcK8ONDPPVv30wVblRgY4qbUmm0uyDm8FhTbtr9LU+EvgQaEN8uofu/LDwCLXIHdPSrk3fmNvAkn7BKjYGsVTJ1asqeT7TYCpptLYpfo0h8H3jDrnrN7I9sKSdST/yrwkdcO6As6ArT8uOMNLST/fhuC2zPBlsNQLEWm2wbbHBgT94Tf6UsRsngw+yV2YxYZ2ceYwal27sVi0S6qtsF5oVCjpe1ZGbkxnioQ1leIL3wJkvXEckfo/RAYgapFJuarleL8hlRd1JZdieVgAmIpy+N5hyI8g/KrKmPM9BJAYHqqHgj6GVQZo/nH1ErSw9rxUPuAEb54tS+V3TkXSic3snDCNNviQtqsZa49AbfJx4MLfN0pseWpFrPsclFb7nlGOVrLsnapd6bVMkHCjOUjaRH6ntof/MghkAq0sKmqE5x9txs/ntSitMY1pFwpNv/ojU42XjF2p+9OEgiMzoJLdV0ov+086Z/gQF7vrEU36dMGWkPQ+PYtHj515FGbvcv/c1UkaEJkPKNFdV+VRWWgh6iJIndIWXRK+PPufl6wnWhREnlQJmJIERlSoNEDUS7RIZ4YNT5Qavi7xkcp2B7yoUZOHGtHJ8c6AjpVY1HBszhCDakfWtdPc9PWcA8ak6WBoM="' --data '{ "flow": "MATCH_CODE", "amount_unit": 100, "currency": "EUR" }' but i have this error: { "code": 52, "message": "Digest doesn't match", "wlt": "CEPCNseA" } I checked the digest (<https://satispay-signature-test.glitch.me/digest>) and message (<https://satispay-signature-test.glitch.me/signature>) and all is correct. What's wrong?

Hi Support Team, We have encountered an issue with Satispay payments on our website. After investigating, we discovered that the problem occurs when users are on a smartphone and use a non-default browser to make the purchase. For example, if Safari is the default browser but the user makes the purchase using Chrome, after completing the payment, Satispay redirects them back to the default browser (Safari). This redirection causes a problem because the default browser does not have the correct cookies to update the order status, resulting in the order appearing as incomplete. To illustrate, an order might be initiated from a browser with the user agent string: Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Mobile Safari/537.36 But after payment, the user is redirected to: Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/112.0.5615.136 Mobile Safari/537.36 XiaoMi/MiuiBrowser/14.13.0-gn This change in browser environment means the cookies needed to update the order status are not present, causing the order to appear as incomplete. Additionally, the same issue occurs if the user starts the order in an incognito session. After payment, they are redirected to the normal version of the same browser. This again results in the cookies not being transferred, leading to the same problem with the order status. Could you please assist us in finding a solution to handle this redirection correctly and ensure that the order status updates appropriately regardless of the browser used? Thank you for your help. Best regards, Andrea

So I'm planning an integration with a funds preauthorization (using the flow "PRE_AUTHORIZED_FUND_LOCK"). For all other payment methods I support I have a way to increase the preauthorized funds if I need to (i.e. I preauthorized 10 euros, but after a while I may need to get more). Is there a way to do so using this flow I'm using or am I missing something? Thanks in advance.

hello, I have a developed an application that create a payment order. When using staging host everything is working fine. The same application was working when I switched to satispay production host. However, after some tests, it is not working anymore in may deployed application and I'm able to call it only in my local environment.

Ciao, sto utilizzando le API di sandbox per eseguire un pagamento. La create mi funziona e mi restituisce un'id che vado poi a riutilizzare nel Get Payment Details. Quest'ultima però mi da problemi nonostante credo di inserire gli headers corretti (la stessa tripletta date, digest, authorization utilizzata per la create). Sto sbagliando qualcosa? Grazie

Buongiorno, ho un problema con la ricezione dei pagamenti sul mio e-commerce Woocommerce con Satispay. I clienti effettuano correttamente l'ordine ma questo la maggior parte delle volte viene immediatamente cancellato. Ho letto questa richiesta per lo stesso problema: <https://developers.satispay.com/reference/firewall-configuration> (ho controllato con il mio host e non c'è nessun blocco di sicurezza). Ho letto anche un altra discussione per lo stesso problema: <https://developers.satispay.com/discuss/63f6790b0558f8006de0c895> ed ho provveduto a seguire la guida fornita: Scaricato il plugin: WP-Crontrol Settato come evento: wc_satispay_finalize_orders_event Settato l'aggiornamento a: ogni minuto Vorrei essere certo che questo problema venga risolto, sto perdendo molti ordini. Grazie e buona giornata! <br>

Hello, I lost my keyIds so now I need a new activation code to generate a keyId again. Could you please provide me a new activation code? Thanks

Abbiamo un problema con il callback url e con il redirect url in 2 situazioni (nella chiamata di creazione pagamento passiamo entrambi gli url, che sono uguali: 1. con iphone se non si usa il browser predefinito (safari) si va correttamente (dal sito) all'app satispay ma poi non si viene reindirizzati al browser e quindi il pagamento non può essere registrato. Se si utilizza invece safari già nella creazione del pagamento, si viene poi correttamente reindirizzati con il payment_id ed è quindi possibile registrare il pagamento sul sito. 2. sia con iphone che con android, se si inizia la navigazione del sito in incognito, si va correttamente ad effettare il pagamento sulla app ma poi non si viene mai reindirizzati all'url di callback e quindi non è possibile registrare il pagamento.

Ho creato un account <https://satispay-sandbox.paperform.co/> Ora come creo un negozio per fare i test di pagamento dall'account di test appena creato?