API Transaction Results

[franklin]

Hi C&P

Confused about a couple points. Can you clarify when a C&P Data record is created? It doesn't seem to be when invalid cc information is submitted but only when correct cc information is submitted and the bank declines. Is this correct?

On my custom forms - I was checking if a cnpxmlstring.TransactionNumber was returned to see if it was a successful request. I think this is wrong. It looks like cnpxmlstring.TransactionNumber are created if successful, if declined, or even if incorrect information is submitted. Can you clarify?

I also noticed the cnpxmlstring.VaultGUID seems to be created only when successful - but not when a temporary contact is created? Is this correct? And if so what do you suggest I use as an indicator of a successful transaction?

And lastly, has anything changed about the API that I should be aware of? I seem to be getting Result Code:5001 / Decline unnecessarily. I have not updated to 8.0 yet.


Thanks
Franklin

[CnP.Support]

Good day Franklin,

The data posts only if the XML is valid. If a valid XML posts the API processor will process and post back to the C&P Data.

If the XML is ill-formed then the API processor will reject connection and it will not work. It is best if you do the following:

• Post the XML
• Go to Salesforce log files and see the XML that was posted
• Take the XML and post it to: https://Verify.PaaS.Cloud.ClickandPledge.com
• Click on ECHO to see if the XML works and no errors are reported

We are working on an update to the API Class Library that saves the XML posts in a log object with the responses from the server. I am sure that your post, if not coming to C&P Data, is ill formed.

Please try it and let us know if we it helps you narrow down the issue.

[franklin]

Thanks C&P

Good feedback. I didn't know about that page. Great resource.

Can you address the questions about when transactions are created and what to test to accurately know if a successful transaction has been created?

[CnP.Support]

Good day Franklin:

Replies to your questions:

Q: Can you clarify when a C&P Data record is created? It doesn't seem to be when invalid cc information is submitted but only when correct cc information is submitted and the bank declines. Is this correct?

Reply: In the absence of any XML errors the data posts back to C&P Data in all cases. If the XML is ill-formed the API will reject it and won't post back to the C&P Data. Please note that if you are ONLY using the API Class Library in the absence of PaaS the C&P Data object will be missing from the instance. You need to install the C&P Bridge to see the data. C&P Bridge is a stand alone application (not on AppExchange) which includes the C&P Data. If you install the Bridge in addition to PaaS we will post to both C&P Data & C&P Bridge.

Q: On my custom forms - I was checking if a cnpxmlstring.TransactionNumber was returned to see if it was a successful request. I think this is wrong. It looks like cnpxmlstring.TransactionNumber are created if successful, if declined, or even if incorrect information is submitted. Can you clarify?

Reply: Please check cnpxmlstring.TransactionResultCode to verify a transaction's success or failure. If a transaction is successful then cnpxmlstring.TransactionResultCode is 0 if the transaction is not successful then it returns an integer value corresponding to the error code (http://manual.clickandpledge.com/Response.html).

Q: I also noticed the cnpxmlstring.VaultGUID seems to be created only when successful - but not when a temporary contact is created? Is this correct? And if so what do you suggest I use as an indicator of a successful transaction?

Reply: cnpxmlstring.TransactionResultCode

Q: And lastly, has anything changed about the API that I should be aware of? I seem to be getting Result Code:5001 / Decline unnecessarily. I have not updated to 8.0 yet.

Reply: Please print the XML file that you are trying to send to the API and process it at https://verify.paas.cloud.clickandpledge.com. The verification service will show you any errors that may be present.