Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


These support forums are now closed for new topics and comments.
Please head on over to http://eureka.ucommerce.net/ for support.

  • Owais Vaiyani 6 posts 80 karma points
    Jul 10, 2014 @ 16:37
    Owais Vaiyani
    0

    Netbanx Silent Post

    Hi

    I am new to ucommerce and I am looking to integrate netbanx hosted payment api. I am looking to use Silent Post option, which basically is 

    1) initialise order details with netbanx

    2) netbanx return a unique url

    3) I will create a payment form (Credit Card Number, Exp etc) and when the customer submits the form it goes directly to the netbanx without hitting our server 

    4) netbanx redirects user to sucess/fail page in on our site

    I would like to know what would be a good approach to implementing this scenario. Should I be implementing the IPaymentMethodService, if so at what point.  

     

  • Martin 181 posts 740 karma points
    Jul 10, 2014 @ 17:14
    Martin
    0

    Hi Owais,

    I have just briefly looked through Netbanx guide (very briefly :D). As I understand you redirect customers last in step two and they do the payment at Netbanx website/hosted page, right?

    In that case I think you should use ExternalPaymentMethodService or AbstractPaymentMethodService  instead of the interface. When using those two abstract classes instead you get some logic from uCommerce handling some parts of creating payments and so forth.

    I don't know whether you have read this article http://docs.ucommerce.net/ucommerce/v6/payment-providers/integrating-a-payment-gateway.html but here you go :) The article or doc should get you started. If you have other questions I (or someone else) perhaps anwer it.

    Best regards
    Martin 

  • Owais Vaiyani 6 posts 80 karma points
    Jul 10, 2014 @ 17:27
    Owais Vaiyani
    0

    Thanks Martin for your reply. No the credit card page will be on our server, but the form action will post the details directly onto Netbanx provided url during the order initialisation. User does not get redirected to netbanx to enter CC details. When the CC post it made to netbanx it will redirect the user to our page sucsesful or failed.

    I am looking at the ExternalPaymentMethodService which has couple of methods which looks like the right ones.. Renderpage() and the RequestPayment().

    But I am not sure which one I need to use or whether I need both depending on what they do ?

  • Martin 181 posts 740 karma points
    Jul 10, 2014 @ 18:01
    Martin
    100

    Okay then I learned something new. :) 

    In that case I think you should use AbstractPaymentMethodService. ExternalPaymentMethodService is build towards a payment flow where you redirect customers to a hosted webpage at the payment provider.

    RequestPayment is used for initialize the payment process. In this case you will call the Netbanx API and get your payment/forms url, and saves this url somewhere you can fetch it again.

    AquirePayment/CancelPayment is used to "capture", refund money or perhaps invalidate an payment. As I recall this is used if your payment provider allows you to authorize a payment and then later you can aquire the money (etc. when you ship a customer's order). So it is not nessacery you need to implement these.

  • Owais Vaiyani 6 posts 80 karma points
    Jul 10, 2014 @ 18:36
    Owais Vaiyani
    0

     
    If you look at the netbanx api you will see something similar as this attached image. Where you see the Process Payment component, I am not sure which of the PaymentMethods to implement. Do you still think I should implement AbstractPaymentMethodService?

     

     

     

  • Jesper Nielsen 141 posts 498 karma points
    Aug 12, 2014 @ 11:42
    Jesper Nielsen
    0

    Hello Owais,

    Could you please close this thread? :-)

    I believe the discussion has moved to the support mail.

    Kind regards,

    Jesper

Please Sign in or register to post replies

Write your reply to:

Draft