![]() I checked my credit card, however, and the transaction went through. I got an email from CP that the payment will not go through and that I am going to continue to receive the email until I cancel the transaction. Today was the first day of the next recurring payment. Given this, I manually set up the recurring on the Transaction Central side, which will then ALWAYS create a discrepancy between the two. Transaction Central sent it up their chain to see why it did not transfer over and I have attached their response. After that I noticed on Transaction Central that the recurring did not come over, it was set as manual. We used API to set up custom pages for donations including recuring. When I signed up for Click and Plege the saes representative said it could do recurring transactions. The WID is 69236 for the form that is referenced below. Is there some additional piece of data that we need to include with the data transmission? Is this a limitation of the API?įor your refrence, our account number is 25991. We would have to manually make that happen. The orders being sent to Transaction Central do NOT include the recurring data. However, now that we are coming up on the first execution of the actual recurrence, there is an issue. ![]() The data is coming across, the system sees it is a recurring donation, and all seemed well. One of these forms allows the customer to set up a recurring donation, and that part has been working fine. We are currently using a custom form using the API to post donations. ![]() ![]() I think it will be obvious to see her frustration. I have posted an email below from my boss to the sales department. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |