This is for developers wanting to use Ordo’s APIs to integrate with our fully hosted platform to issue and manage recurring payment arrangements & payment requests. The APIs rely on RESTful best practices and follow a resource-based URL form.
To access the Ordo Developer Portal, click here:
Ordo has two core ways for businesses to collect money, either via recurring payment arrangements to allow multiple payments of either fixed or variable amounts to be collected, or one-off payment requests to their customers. These APIs also include the generation of each payment transaction.
Variable Recurring Payments (VRPs) enable you to collect regular and ad hoc payments, for fixed or variable amounts.
Typical use cases for this include:
With VRP from Ordo, you can set up an agreement with your customers that allows you to collect payments on a continuous basis in line with the parameters agreed with the customer. There’s no need for the customer to provide additional authorisation for each payment, giving you and your customers more flexibility, security and transparency than well-known services such as Direct Debit, Standing Orders or card CPA.
For businesses that want to manage the initial presentation of payment requests to their customers; Ordo supplies the business with a unique URL for each payment request, which the business presents to their customer via their preferred mechanism, such as:
With Biller Delivery you can tailor the message you give your customers, speeding up cash flow, improving your reconciliation of incoming funds, and reducing your costs, all whilst also making it simpler for your customer to make payments.
This is the simplest service; businesses create payment requests and leaves it to Ordo to deliver the request to the payer; either via email or SMS. This is designed for businesses that don’t have the capability to send the payment requests themselves.
Whichever of the above methods is used, the payer journey that the customer sees can be white-labelled to feel part of a seamless, friction-free journey; reducing abandonment rates.
If you have a need to manage receivables into a large number of different bank accounts, either for your own organisation or on behalf of multiple customers, then you can use the FI APIs to add as many bank accounts to your ‘send’ capability as you need. Typical use cases are banks managing a portfolio of savings or loan accounts, EMIs offering pre-paid card accounts, and SaaS providers operating hosted solutions for multiple customers.
Each payment request would present the name of the account that funds are to go to, providing a more personalised touch to your customer experience. You can also segregate different customers/business lines by creating a range of participant IDs, and associate different accounts and white-labelling to each participant ID.
