Payment method wrong in Click and Pledge

[[email protected]]

We have a form in Gravity Forms collecting payment via C&P. In the last few days we've had a couple of people submit payment with a credit card but their payment method comes through as "Custom". Why is that? We only have one type ofpayment marked as "custom" which is for people who request an invoice and do not submit payment at the time. Custom payment methods do not get posted to Salesforce.It is also not collecting payment. Why is this happening?

[CnP.Support.AM]

Good day @[email protected]

Would you please share a couple of order numbers so that we can review it?

Looking forward to hearing back from you.

[[email protected]]

60191-220802113733421
60191-220725135614601

[[email protected]]

This is now happening on multple forms. I need this fixed. Any ideas?

[CnP.Support.AM]

Good day @[email protected]

We found that you have added a custom payment field that is invisible.

Please see:




In order to fix the issue, you have to remove this field from all of your forms because it will post as a custom payment, not as an invoice.

[[email protected]]

we;ve used this previously without incident. it allows people to get an invoice and not pay right away. why would it stop working

[CnP.Support]

Good day [email protected]

We see the problem .. unfortunately with flexibility of Gravity Form, at times people change the code without knowing it. The challenge is programs need to rely on certain values to know what to do. Two of those values are:

• eCheck
• Credit Card

Please see the image below:




In the Click & Pledge system there is a payment method called "Custom Payment Type" and that payment type is any text other than the system's names. In other words you could post any value as a custom payment type, e.g. Invoice and the system will simply send a receipt with that payment name but since it is not the processor names it will not post as Credit Card or eCheck

If you look at the image you have changed the name of the Credit Card to "Pay with now Credit Card". That text is NOT "Credit Card" and the system finds a mismatch and as such processes it as it is supposed to be.. a custom payment type with that name.

Please change the VALUE field to what it should be and change the label as you want. In other words, you have full flexibility with the label as the is the UI value and not important for the API but the VALUE is critical as that needs to match the requirements.

I hope that answers your question. Please let us know if we can be of any further assistance.