Wispr Flow: Dictation That Works EverywhereStop typing. Start speaking. 4x faster.
Promoted
PaymentKit is a multi-processor billing platform for SaaS and e-commerce. It routes payments across processors, vaults tokens independently, and keeps subscriptions billing even if a MID gets shut down. No code to launch, full API when you need it.
The MID shutdown example is interesting. can the fallback happen automatically without customers noticing anything on their side?
PaymentKit
@alira_salu Exactly! That’s one of the biggest features we have in the Payment Orchestration settings within Payment Kit. You can set up as many fallbacks as you want, so if you have 4 processors, you can decide which one gets tried next, then the next one after that, and so on.
The user won’t know it’s happening, and they don’t have to click submit again or re-enter their credit card information. Payment Kit automatically routes the transaction through your fallback processors quickly and efficiently.
How easy is it to remove a processor without changing the checkout?
PaymentKit
@rosalie_autumn That's one of the biggest features / benefits of Payment Kit. You'll either use our hosted checkout pages or build a custom checkout with our form fields. When you switch, remove, or add a processor the actual checkout page never changes. Instead the payment in the backend is simply routed to the new processor. So no additional code is required on the actual checkout page itself. It's basically a 5 - 10 second swap in your Payment Kit processor settings.
Can I export my tokens and billing data if I ever leave PaymentKit?
PaymentKit
@sawyer_benjamin Absolutely. Since we aren't tied to any specific bank or processor, we aren't beholden to anyone and we're always happy to help migrate your tokens if you ever need them moved. True independence is important to us which is the basis for building the product. When a payment facilitator like Braintree, Stripe, Checkout.com or Airwallex, or an MOR, doesn't migrate tokens, it's usually not because they don't want to. A lot of the time their underlying bank simply doesn't allow it. Since we don't have or need an underlying bank, we don't have those same restrictions, so we're more than happy to assist with migrating them.
For a growing SaaS when would you say adding a second processor becomes worth the operational complexity?
PaymentKit
@upendra_kumar17 Given how easy it is to do with Payment Kit, I would do this day 1. It doesn't really cost anything to have a second processor and everyone should always have a back up. If you go to X.com or Reddit and search payment or merchant account shutdown or even Stripe shutdown, you'll see hundreds of fresh, low risk startups get kicked off their processors. In addition, when you have multiple processors you can utilize cascading, smart auth retries, and smart dunning to increase your auth rates by 10 - 20%. That's basically 10 - 20% of revenue you wouldn't have had without a second processor.
Been using Payment Kit for a few months and I gotta say aside from the simple and seamless integration the product has really delivered. Ive created a few routing rules to test and now am moving the majority/all of our payments through Payment Kit.
The token ownership part is interesting. that's usually the thing that makes switching providers difficult.
PaymentKit
@grace_gui02 Right, and it's the part nobody checks until they try to leave. The processor holds the tokens, so "switching" really means asking every customer to re-enter their card... Painful
@diego_vidal10 That makes a lot of sense. The token ownership issue is definitely the part that gets overlooked until a team actually needs to switch providers. Solving that layer makes the whole process much less painful.
The biggest value here for me is continuity. Customers shouldn’t even notice when a payment processor has an issue.
PaymentKit
@jharkhandi_chora1 Sure! Everything else is plumbing to make sure the customer never has a reason to think about you