Checking this out on my Sandbox account, the Connect button will bring up a page listing the accounts you can connect to if you are currently logged into Stripe. Otherwise, if you are logged out, or never used Stripe before, then you should get this screen below.
It does not matter which payment provider you use for testing. All the Orders and Payments will be generated the same way as internally Keap will just a response back saying if the payment was successful or not. Try it out with Stripe and compare the results between that and the account running Keap Pay.
At the moment, Stripe is the only payment provider we offer for new apps. Support for other payment providers, including Keap Pay, isn’t currently available for new apps.
If your goal is to develop and test against the REST v2 Payments APIs, Stripe will let you exercise the same Orders and Payments workflows, as the API behavior is consistent regardless of the underlying payment provider.
Does this mean Keap Pay will be eventually phased out? I am a little bit concerned.
I may end up recommending to my client that we switch to Stripe on production as well.
Switching to Stripe will significantly increase our merchant account costs. This is a big concern because if we can’t use Keap Pay at our negotiated rate, we’d have to consider going back to TSYS. If that’s not an option, we’ll need to come up with some other way to charge our members.
@Tony_Dietsch, over the years Keap have dropped several payment processing providers.
A few years ago I would have suggested Nexus Merchants as a possible solution, but due to several reasons they have closed their business.
My opinion would be to integrate directly with your preferred provider, but that requires developing or using a third party solution for the checkouts if possible. That way you are in control with things.