Extending CnP_PaaS__PaymentType__c

[Brian Koblenz]

Is there any problem extending the values in PaymentType (from those used for Custom payments)?

[CnP.Support]

Good day!

We are not quite sure what you mean by "extending the values" in PaymentType

The Custom Payment type allows you to add any payment name you wish to include in the virtual terminal & event.

For example in the VT you may add default values in the C&P Settings:


The values added for the default custom payment type will show up in the VT in a pull down menu



As stated earlier we are not sure as to what the question is. If the above does not provide the answer you are looking for please provide further explanation.

[Brian Koblenz]

I understand how to add custom payment types. However, I would like to also have that custom payment type become the actual payment type so I do not need to display both values in my list views and for my buttons and other programs in the system they can just look at payment type. My plan would be to have a non-null custom payment type copied over to the payment type field via an automatic rule.

Hence I would like to add values to the paymenttype picklist.

Does that help clarify?

[CnP.Support]

Good day!

Sorry but we are a bit confused still. Perhaps it is because it is Friday.

Do you want to make the Custom Payment Type with the text added as the default payment type and hide all other payment methods?

[Brian Koblenz]

Ahhh. Communication is so hard. I am not sure I understand what you are suggesting. So let me give an example. (btw, you have login access and my org id is: 00Dd0000000dYD1)

I guess it was confusing (to me) because you already copy the custom payment type to the paymenttype even though it is not a valid value in paymenttype picklist.

So, therefore it must be ok for me to extend the picklist values so one could modify the paymenttype if needed without using dataloader. Right?

-brian

[CnP.Support]

Good day!

CustomPaymentType is an API name and its values are open for posting to Salesforce. Any name may post as the name is customizable.

We are truly not sure what you are trying to do. You may want to join one of our daily office hours & discuss your question - it may help us understand exactly what you wish to accomplish.

[Brian Koblenz]

I'll make one last attempt to explain my confusion.

You have a field CnP_PaaS__Custom_Payment_Type_Name__c. It is a 250 character text field and clearly customizable.

You also have a field CnP_PaaS__PaymentType__c. It is a picklist and is filled in by when a transaction (credit card, echeck) is processed.

It appears (happily) that when a VT payment is made with a custom payment type, that the custom payment type string is copied to the CnP_PaaS_PaymentType__c. So that field now has values that may not be in the picklist. Can you confirm that this is indeed the case? (I did not know this to be true when I started my note and thus am now comfortable that things will work as needed.)

My question was can I extend the values in the picklist and I believe the answer is certainly yes, since, for custom payments, you are putting values in that field that are not found in the picklist.

[CnP.Support]

Good day!

The API has essentially the following payment methods that it will process for:

• Credit Card - sent to gateway
• eCheck / ACH - sent to gateway
• Invoice - no gateway interaction - system will simply send the receipt and include invoice as the payment type.
• Purchase Order - no gateway interaction - system will simply send the receipt and include Purchase Order as the payment type.
• Custom Payment Type: Any text may be passed to the API as the payment method. The payment method name has certain restrictions in Salesforce as the triggers look for certain texts to perform specific action. The restrictions posted e.g. Check, etc. are texts that are reserved. If those texts are used the system will assume the payment is ACH. The validations are set to look for these reserved words.

The default values entered in the VT are simply texts that may be selected in VT so the end user does not have to enter it. It is a feature for keeping the data consistent. When we save we simply save a string in that field. This is why in the absence of default values you have an open text box to enter anything you want.

The value to be saved has nothing to do with the default values entered in the settings. The default values are added by admins to make sure the end user does not type cash, CASH, Cash and caSH in the field since the pull down menu will always save the same value with the same spelling. If an admin wishes to manually put a text in that field in the object then it can be done - it has no relationship with anything else.

Hope that answers the question.

[Brian Koblenz]

Thank you very much for the detail.