Support » Plugin: Paid Memberships Pro » New gateway required checkout fields

  • Resolved nunks


    I’m working on a plugin to add a payment gateway for a brazilian payment service, and it requires additional checkout data (taxpayer id, as well as specifically formatted address data).

    In other projects I used PMPro Register Helper to create a personalized form, but then I didn’t need to send the data to the gateway, just save it to user meta. Now, something tells me this wouldn’t be the right path to follow when implementing a new gateway.

    I see other gateway objects using pmpro_required_billing_fields() to disable fields that aren’t needed, but is there a predefined way to add new payment info fields through plugin code?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter nunks


    Oops, sorry, it took me a while to understand that pmpro_required_billing_fields() is used to set fields as required for form validation.

    I understand, by looking at the structure of the orders table, that the address fields are somewhat constrained to the original design. I think I’ll need to save localized brazillian data to usermeta and simultaneously format it to fit the order object, and then retrieve it from usermeta as needed in subsequent orders, webhook responses etc.

    Still, do you have any advice as to how I can define gateway-specific form fields for the user to fill?

    Plugin Author Andrew Lima


    Hi @nunks

    Thank you for reaching out to Paid Memberships Pro and for building a new integration.

    Due to the complexity of building a new gateway I recommend reaching out to us via email using the following link

    We’d like to put you in touch with one of our developer’s to advise you on the best path forward.

    We look forward to hearing from you.

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.