Create an in3 transaction

The CM.com Online Payments API enables you to create an in3 transaction. The diagram below presents the interaction that takes place between Consumer, Merchant (You), CM.com Online Payments API, and IN3 when creating an in3 transaction:

In the diagram above the following steps are performed:

  1. Consumer wants to start a payment.
  2. Merchant makes a request to create an in3 transaction.
  3. Merchant receives a successful response and redirects the Consumer to the provided URL.
  4. Consumer completes the first instalment payment, and eventually is redirected to the CM.com Online Payments API returnURL.
  5. When the status of the in3 transaction is updated on the CM.com Online Payments API, the Consumer is redirected to the return URL that the Merchant specified in the original request to create the in3 transaction.
  6. If the Merchant also specified webhooks in the original request then CM.com Online Payments API will trigger the proper webhooks and make the requests to the webhook URLs specified by the Merchant. When using webhooks, be aware that they are only a "best effort" mechanism.
  7. Merchant gets the latest details of the transaction. This usually happens once the Merchant received a webhook request.

The API endpoints involved on this flow are:

Create a refund for the payment made with an in3 transaction

The CM.com Online Payments API enables you to create a refund for the payment made with an in3 transaction. The diagram below presents the interaction that takes place between Merchant (You) and CM.com Online Payments API when requesting a refund for the payment made with an in3 transaction:

The API endpoints involved on this flow are:

Get refunds of an in3 transaction

The CM.com Online Payments API enables you to get the details of the refunds created for the payments made with an in3 transaction. The diagram below presents the interaction that takes place between Merchant (You) and CM.com Online Payments API when requesting refunds related to an in3 transaction:

The API endpoints involved on this flow are: