💻Building a Custom Payment Gateway

Prerequisites

• Good understanding of Liquid

• Good understanding of JavaScript

• Good understanding of GraphQL, including queries, related_models, mutations and using mutations to send API calls.

• Good understanding of APIs

Introduction

Siteglide have built integrations between its eCommerce Module and three Payment Gateways:

• Stripe - integrated with all Siteglide eCommerce Features

• PayPal - for Checkout and Basic Payment Forms

• Authorize.net - for Basic Payment Forms

In order to focus on improving features for the Payment Gateways we have, we won't be building integrations to any other Payment Gateways at this point. Instead, this Article is intended to help experienced Siteglide Partners build their own Payment Gateway Integrations.

---

Payment Gateway Configuration

We've opened up the Payment Gateway model (model_schema_name: "module_14/payment_gateway") to allow you to customize it to suit your own Payment Gateway:

Field Name	Field ID	Purpose/Notes
Name	module_field_14/payment_gateway_1	Payment Gateway Display Name
Active	module_field_14/payment_gateway_2	Boolean Only one Payment Gateway should be active at a time.
Type	module_field_14/payment_gateway_5	Payment Gateway Name in snake_case - Must be unique to your Payment Gateway
In test mode?	module_field_14/payment_gateway_8	Boolean
Custom Payment Gateway Partial Path	module_field_14/payment_gateway_19	Folder path for the partials you will use to include your Gateway code on the Form (see next section)

Use GraphQL to create a record in this table using the filelds above.

Next Steps

Now your Payment Gateway exists, it's time to give it some functionality. You can add support for one or more of the following:

Steps to Support Checkout with your Custom Payment Gateway

Steps to Support Basic Payment Forms with your Custom Payment Gateway