Discussions

Buongiorno, ho letto nel Support del plugin Woocommerce Satispay che stavate lavorando per l'attivazione dei pagamenti ricorsivi legati a Woocommerce Subscriptions. https://wordpress.org/support/topic/recurring-payment-support-4/ Volevo sapere se ci sono aggiornamenti in merito e se c'è una data prevista per il rilascio dell'aggiornamento. grazie in anticipo

Good morning, I have a question about this flow: https://files.readme.io/0ab91c3-no_title_1.png When authorization has been approved the Satispay app should make a redirect to our app. We pass the URL to redirect to into the parameter callbak_url: satispay-stag://open/preauthorized-payments/payment?id=c5ff83df-0999-4377-91f6-824e517b5d1d&callback_url=myapp://myapp.com/payments The question is, the callback_url could be an url_scheme such as: callback_url=myapp://myapp.com/payments ? So we can use Deeplinks to intercept the call. In which way the Satispay app makes the redirect? Ours is not a native app so we can't use the Satispay SDK. Thank you Claudio

Hi, I'm trying to implement this scenario, but I think I'm missing something: in our e-commerce, customers can make orders that have to be confirmed later by the admin (or refused), so the payments have to stay in a sort of "pending" status and then updated with accept or deny. I see in your docs the "PUT - Update payment" API, but I can't understand how I can create the order with this kind of "pending" status. Eventually, is there a way to use also the PRE_AUTHORIZED flow with the same scenario as well? Thank you

Hi, I'm trying to do an Authentication Test. public key: -----BEGIN PUBLIC KEY----- MIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEAxuoblYC3ex5k1yh8Y+GK oGCWS9BpQnO7Oqbpa0OB0vujQ+mr0jST6UUFeQBsHnTHgvgVVFbroZf1YCdm2EVn HRWSeWyr3JudhK5vEhfx7Lqh9Ye9PWrawf54armxskx38wvmZMW/I/OvdYRddOes meKqucMTp1kEK9YYT92lWXEJBhurdQW8Nl5zDMGG5HsZkqNpmrmEdCohUbMV3mvz 7mh6gB5n2wn91HGalmzhI2qU4EsjBuaYtFf0Ii0FlDqFOkPFHzWgeMh265qkTClw ZMXjk/zgsiGOYRGaJXjnDjBvB9ZoocyCiYKrG0YdVDHu7SFsfKVpnEP3aZVyCe9a c/eA5XDR1RN992AziBdeThIra/5hDtC8eo3qSODARfag4X31leNipfkN8vQTvgyd 3Aa62wez5tFkQyFtIKRXPUt5xCmb7kp6w7C/pNjbl1JEf/LzoH8V3RlJoYnX9ItB jNty3gwr2MMcKFw3desM2JyHcZBhT4PFymRTpJypej2kMB238MQHBGWN8iFtUnhJ jYT1VmK/SqAxIvC5EL1rKid/Ew26WpVmK38sDASPojcvEVRTNGUlATra95tsTpMs 3KuNyOe/6LwZxlAWJsy0MQHS0UDjUTft8tWhRqvxKC7uSvQElLkv9+MibPghmwEf JKGXTQy4WW2P9kHdXCuNNpMCAwEAAQ== -----END PUBLIC KEY----- private key: -----BEGIN RSA PRIVATE KEY----- MIIJJwIBAAKCAgEAxuoblYC3ex5k1yh8Y+GKoGCWS9BpQnO7Oqbpa0OB0vujQ+mr 0jST6UUFeQBsHnTHgvgVVFbroZf1YCdm2EVnHRWSeWyr3JudhK5vEhfx7Lqh9Ye9 PWrawf54armxskx38wvmZMW/I/OvdYRddOesmeKqucMTp1kEK9YYT92lWXEJBhur dQW8Nl5zDMGG5HsZkqNpmrmEdCohUbMV3mvz7mh6gB5n2wn91HGalmzhI2qU4Esj BuaYtFf0Ii0FlDqFOkPFHzWgeMh265qkTClwZMXjk/zgsiGOYRGaJXjnDjBvB9Zo ocyCiYKrG0YdVDHu7SFsfKVpnEP3aZVyCe9ac/eA5XDR1RN992AziBdeThIra/5h DtC8eo3qSODARfag4X31leNipfkN8vQTvgyd3Aa62wez5tFkQyFtIKRXPUt5xCmb 7kp6w7C/pNjbl1JEf/LzoH8V3RlJoYnX9ItBjNty3gwr2MMcKFw3desM2JyHcZBh T4PFymRTpJypej2kMB238MQHBGWN8iFtUnhJjYT1VmK/SqAxIvC5EL1rKid/Ew26 WpVmK38sDASPojcvEVRTNGUlATra95tsTpMs3KuNyOe/6LwZxlAWJsy0MQHS0UDj UTft8tWhRqvxKC7uSvQElLkv9+MibPghmwEfJKGXTQy4WW2P9kHdXCuNNpMCAwEA AQKCAgBpvQ0IvjHK+u80CMuG9OASPQXoK1OpBYhjt1KhuHMMysORWGgEB/sQp6Yv GnBfCEj+cA42lTYQ4oyHnqpnEQ2tQkhoz8HUNczYOTnF7oCmDNgHgy6vtVuwgCtW 4Ht7gnbI9mx06UGgROvilohvmq//5aRHt1F9Ri6XdunZmsNI9nOLka3lOTVB2Zdj EoU4c8+2SbPbkf69GaA4o/BeGhjDhTqJXKBsqbUK95DrodlUUFXvnUFza6WFSLP4 buJmV212+YuR+ZniWv4MZFouOmEK0L8Xbfer+XaMVyUQAmMhAdIj4nAggmxp2NJI X0878IdH+tqGsA+iB+c/czf53AjCaKgpVXPWU7+z8XqIqhwm/+sJxn3yDzbQgDRV 6Hf8MHdI50IxXRfB0QlvRMlbx/NPSAAfys81C0riwRnoweTDHnMrXW/a3HPohtDe RML2RzOStQM+3nOk84zqbQ9vmDsZlSTjGckjsFAmXfLqVrNiep0aL2hDmmidRtLR LbF+31xFuWiAeNNPsglvI0Ew2eh9K4V26V2Z9vpe8wgKxow5ce8ukdLDb/SMrQKG Ib/LHvDzrXPqV3vqzQewwyw822DvX+sMKn/T13kO2rDgwSYGOerJMpyw4LXhBtx2 Y0g9ODTCa6TiHQ//WhjJekSiMVBrDoxLv9OjwSq9icVI9xcQgQKCAQEA6POvg7l+ 4HDxJsJ3909X+JE0EaiK/WRDqGGQhKeC9r1CoqZKv+JikBeomjzHoQZq0QD8mWnU C+/xOsPEVJXoIGuDUl8JyM+oZz1m4hvifawFI70EPtthxnl9qRkgeeFPsPCxcFCq tnKrcmsaF5v/LyNr4bkjWrCQ4r/w5ur3ENeMgDdP61cOMdVlApADxXIuPAx6v3UN ZSuW0WFFUNjOFmIQSoh1fr7Y99IG7GWBUDiub+32VQ3il2I4kAiZ5LEXSlQC1+8x KveNCHpq4nRDJFPjIkuMu7MLRXJYedIG2yFbxdvxL/2N/YjXRkTABQa9x/8fTheW Vij3E1SlH5zScwKCAQEA2phOgG89Qyh61Uuout3LBhXGZZ30Qr0FPnjCQmSmbRLy vaidZpjyaUa1PNa1ZJaFoOXi/p4Fd5tl2Cp03vogqbz7gzGaej2u6LxygcUE1meG qk9+GH/xNfbweCpbyxs9Ynv/+GYcVFLnwb2Z6D0Qhl0BjHvp43ptff2EeKkB0u+b 6qSqTSFMTKrcLuVjx7cetTgGfK2jHiez6Rcs1Czk9ueZg0UFRM0PAEf2zqrdQ1g/ Etb3WOU1PCanEWhhC8svlff59XMcp77BOZ6ARqu/e7J+CHIl4k6dVwgyHFJq6PEV VGeG/ttoIfFxse91OdTLcOpUmf5tMtZVQYfbcoVjYQKCAQBIEyWJ1vm3jZo/SMn/ XbA1Ow/mKsSeM8hvL4icUovFtbcJRfQ4vF2MgZVr60REwQyJkAmXmdO+wcVcTjfP h/YjGcCu2rLXS9Cp6KiNat0/ztpkPVYz8IKm+u3zRM/0hc63SzFLM9otyvra0uJm zaA9wHLfiv2yUJDzZzms6KP6tQZGoVZ71RqSNpkjGtXf4D0H3UCZPikf1UW7kKH2 qq3Q5RRvSxs3VOsiefwkZh+FZ5QpE3I0zK//8KbZgZ/DzzsKh0W988a9qYwcRGwP lrMzaTUMZl2rsXDaUs+nGWF/qSmQ5UUReRzWheE9X4YdyAEuAPR5n/imvdP8SiMw zb+bAoIBAF1waW4BHuDMNuVh9/gYwqYRPMNHJ5g3kDxKBk+3EmThip2Dq/SlQEm8 DdC5vsQGi4xheAx6o7+iz3/9dgOyS7ACtkg4Nd4268NUemX6P70ed7PpUu9KEWON 8PCMurwxIqYsdxhJHab14Vcxos5g++VTcEwK08mHFbKbYbrqE3uFLNK6HInnx+Ol zYTGTUabgibYkf1Ng8JqGj9yxpjTr/PSwA4avMvSE619FYT2CKq22A9HkGeRYpYZ t6R7R7Bw5CBo5ZID6KXTpmjo1dBfrfREMheOI59/F0aSnEj6+fQkyYdQ0aWzR+nq eT0kLKnRyjy0DgHdffQTJlJirm1fk0ECggEAdMgYbXxFniPFJLGhfJevj9CUWh9i hfCFuTmdzVmL+N3uFtTjpIuLObw53HYWZi8tdUwDdOmDeSfW64GZuF5iAyqbISV4 Mdt0389BDVmWbnDjFvLwlYHKbn9R71BHoMM9ETu2GHtfHf6DmJ+2EIe+GSrXeDYK CJ5VD6JreLX4OjL4vrBj+yuOeaWURLLkm0SjqK326xLQ6+h4zEMnI/JprOVKObt0 W6zpeskS77RCijweeGpt6c7aytGWrv6Nx0YNWBDChgnKjaFJS5NObS/UXu2o3cL5 Qp4dGpZxgwYPqSi1tTKyv0E4fd5DPD60Qt570/lbbPHODBx6Hmx2eunv0A== -----END RSA PRIVATE KEY----- keyId: vmkhqr4c41u9p2mv2sr0l35a6r0eb3v0uqffgd5cptcr7nm1b0pe9t8v2hobeuic8afbomhgfhgfbbv6ntv1or5q0n8cc5pe55ggtvnn9e4mkcdpkmencvmu14fvs18ov8id9e4suamrj9in9kndlln872kojqcmdtdpp8vmt2cgri4in6msejbp27rc07d54aandube digest: SHA-256=ZML76UQPYzw5yDTmhySnU1S8nmqGde/jhqOG5rpfVSI= uri: https://staging.authservices.satispay.com/wally-services/protocol/tests/signature headers: Accept => application/json Date => Tue, 05 May 2020 14:29:18 +0000 Host: staging.authservices.satispay.com Authorization: Signature keyId="vmkhqr4c41u9p2mv2sr0l35a6r0eb3v0uqffgd5cptcr7nm1b0pe9t8v2hobeuic8afbomhgfhgfbbv6ntv1or5q0n8cc5pe55ggtvnn9e4mkcdpkmencvmu14fvs18ov8id9e4suamrj9in9kndlln872kojqcmdtdpp8vmt2cgri4in6msejbp27rc07d54aandube", algorithm="rsa-sha256", headers="(request-target) host date digest", signature="xc/allCP6F2l4pN+/k/YYGrRSqVIP/Pd02TRKFlLHBq+wcGZGv2FE1QBblvhHPvAE7BDlboljyJkuvBbZAy77sBGjEU4x3xgv91QQh/w1VKwlipwMbKKTAi8kXNc/ly4Opqz6XPTOg5kvdxGpuzj2ny4OcxwxabElWfuIULmoxFuSumA2EV3qbEg6v7ex7fCJuSOrgWjotS6DXNXhE/AqI8udaxSXsqzKlGJspOrMxTfRRtUiXLd7ZIJhTuZyPAO3/8UaO9w2SjrRayYquQs1LWYFBN2O0aqSFVhcb7AoOJYLIq9gyxbJPkyVetEptlO9TRAtga1+NNlQNyVHkfFHie0W7BDmLkrBMhroQ9h54rexx88JO/GP+DWlD6igTgHh1c7/8chlvKj/SIsiT6aOO29MWsidbk06GfzOkrZm/zvIBx934gDWW15h9EzRIa5hcc7EJdaPF2F4nEiOhUFxNpMubErBdSpV7GzIl4jGBY2ofZp8hOw4/JRoQRAiW9stwwc/v5JAFfu8LzFEnnGK0hI95oi88nvV+5G6/YTUb1sZUv0fS5rsQuw4GMaiWUyAExmtBSIE6JG1vqvbg/bFiUxpBy5ewCw29IJ26AR7IgMzV7EnXx8+5ovKXziZOL+S6t7IVadAW4dyHr6ouPWwqr4TL3JMBFlKZEesZkiz/A=" body = "{\n \"flow\": \"MATCH_CODE\",\n \"amount_unit\": 100,\n \"currency\": \"EUR\"\n}"; string "(request-target): post /wally-services/protocol/tests/signature\nhost: staging.authservices.satispay.com\ndate: Tue, 05 May 2020 14:29:18 +0000\ndigest: SHA-256=ZML76UQPYzw5yDTmhySnU1S8nmqGde/jhqOG5rpfVSI=" THE RESULT IS 403 FORBIDDEN BUT AVERYTHING SEEMS CORRECT

Buongiorno, avrei bisogno di un aiuto per un problema con i pagamenti satispay su woocommerce. Dopo l’avvenuto pagamento da parte del cliente lo stato dell’ordine su woocommerce rimane “in attesa di pagamento” e quindi non ricevo avviso dell'ordine ricevuto. Questo non avviene con altri tipi di pagamento ma solo con i pagamenti satispay. Avreste qualche suggerimento su come poter risolvere il problema? Grazie Manuela

Hi there. In the Mobile app payment flow for iOS the documentation states that the following url scheme must be opened: satispay://external/generic/charge?token={payment_id}&callback_url={url_to_open_after_payment_approved} Is there a way to specify an different URL to deep link to if the payment is canceled by the user? Either that or appending a parameter to the provided url (something like ?approved=true or ?canceled=true) would be useful to handle both scenarios differently in the caller app.

Hi, I've obtained the KeyId using the dedicated API, but I've not saved it and I lost it. Now when I call the api with Activation codes for Authentication (token property in json body of post) provided during the account creation, I got only a 403 error with this body { "code": 45, "message": "Forbidden", "wlt": "wiR2WUAk" }, that means Token already paired. How can I obtained a new KeyId? I'm using a sandbox account. Kind Regards

Hi, I'm trying to autenticate in a sandbox environment retireving keyId. I'm making the request in PHP on the Laravel project with: ... \SatispayGBusiness\Api::setSandbox(true); $authentication = \SatispayGBusiness\Api::authenticateWithToken("CODE_RECEIVED_IN_EMAIL"); ... The response is: Exception (45) Forbidden, request id: KN62Tp0H in ...\satispay\gbusiness-api-php-sdk\lib\Request.php220 How can i make the activation? Thanks

Salve, potreste darmi una indicazione sul significato del codice di errore: {"code":46,"message":"Unsupported media type","wlt":"3PphCsbA"} Sotto riporto la richiesta di autenticazione. Grazie e cordiali saluti curl --request POST \ --url 'https://staging.authservices.satispay.com/wally-services/protocol/tests/signature' \ --header 'host: staging.authservices.satispay.com' \ --header 'date: Wen, 16 Dec 2020 18:24:05 +0000' \ --header 'digest: SHA-256=RCtf9dVtFQlDmKB2lBPSibcYiQHIcLJWsKjWG9HQvnU=' \ --header 'Authorization: Signature keyId="o6s6g9qcfkc5fmiud97himsb45g9fc1oj80nnfnod0fu1opq7525jd5d2net4gm4ppro71bjjedj18d2653p778efppg8d2rici61b53sfup1kovlbst7spaldo5dc8nkck1u7o18ta6ikahl4nvrlimhbsjjj07kg1skls8c1qsf8r26a9ue3922a786jlfav6pd6n5", algorithm="rsa-sha256", headers="(request-target) host date digest", signature="BeuNc/XuUTQibhha5U1spm9r61CteHVJpP0JDMQdXtslm3kEWfvUnm7bnxP1GgP+xbCKUI7k7tbbifAibWvIfNogeihv/kdwmGf3TVp+Smb7SZwngRG4t+7CaEuls1uiFrZvcvzOElGpTvb3lYwVkQcfhLXIg3qinVRYU03Z4Mrpdvy62AGAcmaTL8cpue44tHsAc1aMpecl/9+ZX8KNv/sXEiBwHEraBECVL2T5p5BAKLTM2X0ZVUvUUQXOnOM0xvojiSLrglPEQJNNiIoUyfXTHCIYRmgPz/bbgPCAOObrr/9Ax9Oe/ITOGBFj8ye9UdwY83LKeJj6kb+XMMCGM45hHZLxRXkknQDmC7btRBmzSPNW1Mnw/XGoFFdMheQ2te/M2p2yb5ByXS8Ubsu7wUOn6bsRDV0bXQKCMms8Qnk3wCWYE4SkEfaTql2YxJjUKDLiKYzaIghPcRTHdpcGNuyAd46f/5LbR5NomUs5NE+1Jynhcwwzg3zAGeDJkgWXQuEKmh/VZsz8hrNddroQFiADXzwr6YvFhcx9pzuwvtIYwCHGanYkMqoeayQVFZCDU8g72Hehadud7U0cKlFSgRQJn+vknXV5SkXnhg/gb4ltKX6rNMlrcQWX5RzEqrjmz56LC7sLNCwd3xZVWVdmlYW2Z8SLq/gbSlAF72H3EdE="' \ --data '{"flow":"MATCH_CODE","amount":"89999100","currency":"EUR","external_code":"my_order_id","callback_url":"http://localhost:56993/checkout.aspx","metadata":{"order_id":"my_order_id","user":"my_user_id","payment_id":"my_payment","session_id":"my_session","key":"value"}}'

Buongiorno, ho implementato la funzionalità di Web-redirect e funziona tutto corrattamente via desktop. L'unico problema che ho riscontrato sta nel fatto che quando un utente effettua tutte le operazioni da mobile (quindi utilizza lo smartphone a partire dal login del mio portale), al redirect su satispay gli viene aperta in automatico l'app. Dopo il pagamento effettuato con successo, viene rispedito alla pagina di partenza del redirect. Così facendo non vengono scaturite tutte le operazioni contenute all'interno del parametro "redirect_url" proprio perchè la pagina non viene minimamente richiamata. Come posso risolvere?