Payment gateways
Stripe, PayPal, Apple Pay, Google Pay and local gateways such as KHQR, working in your app or site.
- Stripe and PayPal
- Apple Pay and Google Pay
- Local gateways
Part of Payments & connections
Let partners, apps and websites work with your system
We design, build, document and secure APIs for mobile apps, websites, partners and internal systems — versioned, rate-limited and monitored, so what you publish keeps working.
Flexible payment, agreed with each business.
Gateways and channels we connect
- Cards and wallets worldwide
- Checkout and payouts
- Bots, notifications and enquiries
- Business messaging and bots
- Card and QR checkout
- Bakong QR payments and bank transfers
If your provider is not here, ask: most expose an API and we have connected many of them. Names and marks belong to their owners. We build with these tools; no partnership, endorsement or certification is implied.
Let other software work with yours
An API is a promise: send this, get that, every time. We build APIs that keep the promise — clear design, proper authentication, versioning that never breaks an existing client, and documentation a developer can use without ringing you.
We build APIs for the products we run and for clients whose apps are built elsewhere. You get an API specification agreed before code is written, a sandbox for your partners to test against, generated documentation, and monitoring that tells us about a problem before your customers do.
Why have it built by Baal
Designed before it is built
The specification is agreed in writing first, so your app team, your partners and we are building to the same contract.
Documentation people actually use
Reference docs, examples and a sandbox, so a partner developer can integrate without a meeting.
Secure and rate-limited
API keys, OAuth, per-client limits and audit logs, so you know who is calling what and can switch anyone off.
What we build
APIs for mobile and web apps
The backend interface your app and website call, built alongside or for another team's front end.
Partner and public APIs
APIs your customers, resellers and integrators can build against, with keys, quotas and documentation.
API documentation and sandboxes
OpenAPI specifications, reference docs, code samples and a test environment.
Authentication and security
API keys, OAuth 2.0, signed requests, permissions and rate limiting done properly.
Versioning and migration
New versions rolled out without breaking the clients on the old one.
Monitoring and support
Uptime, latency and error alerts, with fixes on a support plan.
Explore this division
Telegram & WhatsApp bots
Orders, bookings, alerts and support in the apps your customers already use.
- Telegram ordering bots
- Booking and appointment bots
- Notifications and alerts
Systems that talk to each other
Accounting, ERP, CRM, delivery, SMS, maps and marketplaces, connected.
- Accounting and ERP integration
- CRM and marketing platforms
- Delivery and logistics
Payments & connections
Take payment any way your customers pay, and make the systems you already run talk to each other.
- Payment gateway integration
- Subscriptions, credits and top-ups
- API development and documentation
How we work
- 01
Talk
You tell us what you need, on WhatsApp, Telegram or the form, and you are talking to the team from the first message. We ask questions until we understand the problem properly — usually the same day.
- 02
Quote
We put the scope, the fee and the timescale in writing before any work begins. No surprises later.
- 03
Build
We build in stages and show you working software as it progresses, not only at the end.
- 04
Support
After release we stay on for updates, fixes and changes as your business grows. Ask for a change and it is done in days, not queued for next quarter.
Frequently asked questions
REST or GraphQL?
REST for most business APIs, because it is simple and every developer knows it; GraphQL when clients need flexible queries over rich data. We recommend and explain the choice in the quote.
Can you document an API we already have?
Yes. We read the code, test the endpoints, write the specification and documentation, and flag anything that should change before you show it to partners.
Who owns the API?
You do, as set out in our terms. Code, documentation and repositories are handed over.