Payment, Shipping and Logistics APIs
Payment, shipping and logistics APIs join checkout and dispatch into one process. They cover serviceability and charges at checkout, payment verification, waybill booking, and tracking written back to the order.
Where orders get stuck
Each system works on its own. Failures appear at the joins, such as a payment that succeeded at the bank but shows pending on the store, or a parcel booked twice after a timeout.
At checkout
Two checks decide whether the buyer can complete the order. Delivery must be possible at that address, and the charge must be known.
Dispatch and after
Dispatch involves many repeated steps for staff. These are handled through the same order screen.
Frequently asked questions
Do we need an aggregator or direct courier accounts?
It depends on volume and partners. An aggregator is simpler to start with and gives several partners through one connection. Direct accounts can be added, with rules deciding which carrier takes an order.
Whose accounts are used for payments and shipping?
Yours, in your business name, with settlements going to your bank. The connection is built against them, and GullySystem holds no credentials beyond what configuration needs.
What happens if a courier API stops responding?
Bookings queue and retry, and the desk is alerted. An alternative partner can be used where your rules allow. An order is not marked dispatched until a waybill returns.
Tell us what you need.
Share your requirements and one of our engineers will come back to you within one business day.
- No obligation
- A reply within one business day
- Your details stay private
Start with your requirements
Seven short steps that tell us what you need. An engineer reads them before getting in touch.
Share your requirements