Git Product home page Git Product logo

Comments (4)

matthiask avatar matthiask commented on July 23, 2024

@arteme, the IPN URLs we have are never visited by customers; those endpoints are only used by the PSPs. I think it's correct to send 403 errors when the parameters cannot be parsed.

Once past the confirmation point, the payment processors have full control over the request/response cycle. You can add as many URLconf entries and views as you want as long as they are contained inside the payment processor class. It should be easily possible to add the REST call and issue redirects and/or error messages afterwards in process_order_confirmed.

Please get back to me if you're having problems again -- maybe paste the code somewhere where I can see it, it might be easier to give pointers.

We are always interested in additional payment processors inside Plata btw!

(And sorry for not answering earlier, I missed this issue somehow.)

from plata.

arteme avatar arteme commented on July 23, 2024

@matthiask, you're absolutely right, IPN URLs are never visited by the end-user.

Quick off-topic question: are Ogone and PostFinance IPN handlers ever used? They are not actually referenced from anywhere.

I guess my real question boils down to the following use case:

The payment processing server may return an error code and error message from its REST call. It would be good to display this message to the end-user. Currently the basic shop "order_payment_failure" doesn't take any additional messages to show to the user. While I could very well override "order_payment_failure" URL in my own show instance, would it make sense to rather add this functionality to the default Plata shop?

from plata.

matthiask avatar matthiask commented on July 23, 2024

Yes, those IPN handlers are definitively used; the callback URL is to be entered in the merchant interface of Ogone/PostFinance. The Ogone/PostFinance servers (it's the same with PayPal by the way) send a POST to this IPN URL as soon as the buyer confirms the transaction. This URL is only used for a server to server request, never by the client.

Concerning messages: I'd use django.contrib.messages everywhere and I think that this is sufficient for all feedback to the user.

from plata.

matthiask avatar matthiask commented on July 23, 2024

I think this issue can be closed?

from plata.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.