1.How do I authenticate with Usio APIs?
This is usually the first step: How do I start talking to the API?
Usio keeps it simple. To authenticate, all you need are:
- Your Merchant ID
- A Username
- A Password
That’s it. No OAuth dance. No token juggling. No complex key management. Just drop those three credentials into your API requests, and you’re good to go.
For sandbox testing, we provide predefined credentials—no setup needed. Just copy, paste, and start building. To make it even faster, we include pre-configured collections for Postman, Insomnia, and Bruno.
2.Does Usio use webhooks?
Ah yes, webhooks—the backbone of many payment platforms. You’ve probably built listeners for events like payment_succeeded or customer_created.
At Usio, you don’t need webhooks for most API calls—we return immediate responses. For things like batching or ACH returns, you can just hit a reporting endpoint once a day to get everything you need in one go. No missed calls, no retries, no confusion.
That said, we do use webhooks for:
- Enrollment (e.g., merchant account status changes)
- Hosted Payment Pages (e.g., when a customer completes a payment)
Since those happen outside of your API requests, we’ll ping you with a webhook when something changes.
3.What’s the best way to collect payment info?
You’ve got three solid options—pick what fits your tech stack, timeline, and user experience goals:
- a) Hosted Payment Pages
A fully customizable form hosted by Usio. Perfect for donations, subscriptions, or invoice payments. You control the branding, fields, and flow. - b) Usio Checkout (Embedded)
Choose between a prebuilt UI that you can drop onto your site or a fully embedded version with custom fields. Either way, we securely collect the payment info (card or bank), so nothing sensitive hits your servers—keeping you out of high PCI scope. - c) API-First Approach
Want full control? Build your own UI and interact with our APIs directly. It’s flexible, powerful, and can be used alongside Checkout.
4.Is there a sandbox? How do I test?
Definitely. Each API comes with both production and sandbox environments.
We give you:
- Sandbox credentials
- Example requests
- Downloadable collections for Postman, Insomnia, and Bruno
You can simulate transactions, test account flows, and see real API responses—no real money involved.
5.How do we handle API errors?
We’ve all been there—staring at a vague 500 error and wondering what went wrong.
Usio gives you clear, consistent error responses like this:
json
CopyEdit
{
"Status": "failure",
"Message": "5000: Invalid account number"
}If “Status” is “success“, you’re all set. If it’s “failure“, you’ll know exactly what needs fixing.
Clear errors = faster debugging, especially during those late-night deploys.
6.Can we migrate from another payment provider?
Absolutely—and we’ll help you do it.
Whether it’s token migration or sub-merchant mapping, we’ve done it all before. You won’t be left guessing. Our onboarding team works with you step-by-step to make the transition painless.
No black-box migrations. No “good luck” emails. Just real support from real humans.
7.What kind of dev support do you offer?
We’re not the kind of platform that drops a 300-page PDF and disappears.
Here’s what you actually get with Usio:
- Clear API documentation and integration guides
- Collections for Postman, Insomnia, and Bruno
- Day-one sandbox access
- A dedicated integration team
- Access to real engineers when you need them
No forums. No bots. Just helpful humans who answer emails and actually pick up the phone.
