Announcement

Collapse
No announcement yet.

Payment Capture Function

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Bruce - PhosphorMedia
    replied
    That's not quite what the function name means. Its the basic function that actually SENDS the data. Whether or not the charge is authorized or auth/capture depends on the values you send in the "data" packet to the authorizing service. This is just an updated version of an older method of sending data. Many new payment features are not available if you don't use the update version.

    If you haven't already, you should review the PaymentModule_ functions in the API doc.

    https://www.miva.com/pdf/MM_Module_A..._Guide_v45.pdf

    Leave a comment:


  • BPS
    replied
    Hi, we are using PaymentModule_Authorize function i will change to PaymentModule_Runtime_Authorize but we want to have plugin to work either authorize only or capture so for capture do i need to call another function

    Leave a comment:


  • Brennan
    replied
    The legacy authorization means you are not using our latest APIs functions for payment. See https://www.miva.com/apiguide (page 151) You want to make sure you're using the PaymentModule_Runtime_Authorize function to handle the authorization.

    Without seeing your code, its hard to say why your capture is failing.

    Leave a comment:


  • BPS
    started a topic Payment Capture Function

    Payment Capture Function

    Hi,

    we are creating a custom payment module but unable to capture payment and payment is showing a legacy authorization in admin and not able to capture.

    can someone please help
Working...
X

This website uses cookies to identify visitors, track visitors to our website, store login session information and to remember your user preferences. By continuing to use this site you agree to our use of cookies. Learn More.

This website uses cookies. By continuing to use this site you agree to our use of cookies. Learn More.

Accept