Manually add integrations

Overview

Loop was built to be extremely flexible. Users can leverage our SDK and APIs to integrate with any payment provider that allows for webhook listening and API writing. This setup for manual transaction signing requires additional integration with the Loop API endpoints described below and is a general guide; the exact integration will depend on the provider.

If you have questions or would like help, please reach out to us at [e-mail]

Step 1: Listening to events

This setup assumes the subscription management platform will autogenerate the invoice. You will need to listen to the relevant event notification that will inform you when an invoice is ready for processing. For example, this object is a Stripe Invoice object.

Step 2: Creating the Loop Transfer

Using the invoice that is generated, you then need to convert this invoice into a Loop transfer request for on-chain processing. This requires you to pull in the relevant information from the generated invoice and using it to populate the relevant field for Loop. When sending transfer requests, most companies opt for Loop to sign the requests, but companies can optionally leverage our SDK if they prefer to sign transfer requests themselves.

Step 3: Listening for the Loop Processed Event

Loop will process the transfer on the billDate. When the transfer has been processed, Loop will emit a webhook with the transfer details.

Step 4: Updating the Invoice

After the Transfer has been processed, the Invoice needs to be updated in the external subscription management system. Find the relevant method to update the invoice in the external system's API documentation. This tells the external system that the invoice was paid out of band, resulting in the subscription being active and up-to-date.