Skip to content

Overview

The iwocaPay ecommerce API is a REST API. It has predictable resource-oriented URLs, accepts form-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs.

You can use the iwocaPay ecommerce API in sandbox mode, which doesn’t affect your live data or interact with the banking networks.

Base URLs

iwocaPay’s ecommerce API endpoints are accessible at a base URL. The staging environment and production environment use different base URLs.

You must use HTTPS for all interactions with our API.

Use the staging environment to develop and test your integration.

https://stage.iwoca-dev.co.uk/

Authentication

All requests require your access token as a header to authenticate against our API. The following example shows how to do this in Bash, Typescript, Python 3, and PHP. You might use similar code to create an order via the iwocaPay API.

Terminal window
curl
-X POST
-H 'Authorization: Bearer SUPPLIER_ACCESS_TOKEN'
-H "Content-Type: application/json"
-d '{"data": {"amount": 4200, "reference": "#order1"}}'
https://www.iwoca.co.uk/api/lending/edge/ecommerce/seller/SUPPLIER_UUID/order/

Get an access token

Request your access token from your account manager. See the Contact us page for more information.

Redirect URLs

redirect_url contains a URL, describing where iwocaPay should send a customer after they have checked out and completed an order. This URL should be to an order confirmation page or somewhere which represents the end of your transaction process.

redirect_url is defined when we issue your access token, and is the same for all orders.