Rapid API recurring payments error

  • Resolved scottrowdy

    (@scottrowdy)


    8 years, 9 months ago

    Hi There,

    We just implemented the Rapid API via user/pass/encryption key for a recurring payments form. The form is now producing this error on submission:

    “The ‘RebillCCNumber’ element has an invalid value according to its data type.”

    I have not had time to debug into what might be occurring. But I think this error is coming back from eway.

    We have reverted that form to legacy XML API and the recurring payments are working again. Does the Rapid API not work with recurring payments yet?

    Thanks.

    https://www.ads-software.com/plugins/gravityforms-eway/

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author webaware

    (@webaware)

    G’day Scott,

    It sounds like the CC number is getting encrypted by Client Side Encryption — I thought I had that sorted out, but maybe not so much!

    Does your form conditionally display the Recurring Payments field, or is it always on? Can you please export the form as .json and send to me via support (at) webaware.com.au?

    Forms > Import/Export > Export Forms

    FYI, Rapid 3.1 API doesn’t do Recurring Payments. It allows rebilling from a token payment, but does not do automatically rebilled payments. This plugin still uses the Recurring Payments XML API, which doesn’t support Client-Side Encryption.

    cheers,
    Ross

    Plugin Author webaware

    (@webaware)

    @scottrowdy thanks for the bug report. Please update to v2.1.4!

    cheers,
    Ross

    Thread Starter scottrowdy

    (@scottrowdy)

    Wow thanks, fixed before I had time to export the form!

    I just updated and tested it. It works perfectly! thanks again.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Rapid API recurring payments error’ is closed to new replies.