In this article, we summoned helpful tips to help you with Solid API integration. 



TABLE OF CONTENTS



SolidGate API is a full host-to-host REST API. Parameters are transmitted via the POST method in the request body (JSON format). Merchant host the Payment form on its end.



Kindly note: You must have an active PCI DSS certificate to work with recurring payments using a host to host connection. If you have no such certificate - you can use the "Solid" payment form to perform payments.



Access to SolidGate API


    Authorization is required for transmitting requests to SolidGate. It can be granted by signing requests to our API. The control signature of the payment notification details allows to verify the source and the integrity of the payment notification details transmitted between merchant and gateway. 


    You should apply the merchant ID and its secret key to generate the signature. Please find detailed instructions here


SDK Kits


    To make the integration process frictionless, we summoned together a set of SDK Kits:


Dev docs here.


Operation types


Charge transaction


    Charge request - basic operation of funds withdrawal from cardholder's account. This operation can be made via 3-D Secure. When the operation is successfully done, cardholder data is tokenized so that the subsequent payments can be made by token (recurring or tokenized transactions).

Dev docs here.


Recurring transaction


    Operation of the recurring payment. In contrast to Charge, the token previously received is to be sent in the request instead of cardholder data.

Dev docs here.


Resign 1-click


    Resign 1-click allows you to perform transactions via token (1-click payments) but also requesting a CVV from the user to additionally verify the transaction.

Please note that this request is available only for PCI-DSS certified merchants. 

Dev docs here.


Check Order Status


    Check order status is a request for getting the current order status.

Dev docs here.


Refund transaction


    A refund is a request for transferring funds back to the cardholder. Refunds can be made only for successful transactions. 

Dev docs here.


Auth transaction


    AUTH request allows to check the availability of a required amount of funds for a specific credit card and reserve it for a subsequent Settle. Funds can be on hold for up to 7 days, if Settle does not take place - funds will be unfrozen. 


    Zero dollar AUTH transaction allows you to verify a cardholder's payment information upon acceptance without actually billing the customer or reserving any funds on his account. This type of authorization request is beneficial for merchants offering trial periods for a product or a service. The cardholder's details will be tokenized, though, allowing you to charge the card when necessary.

For example, you may choose to collect credit card information during an initial registration process and offer a 30 day trial period before actually charging the customer's credit card.

 

    Some issuing banks do not support $0 authorization and may reject the charge request even if all card details are accurate. If the issuing bank rejects the $0 authorization request, we will automatically send a follow-up request with a $1 value amount or equivalent in the applied currency.

Dev docs here.


Auth 3D transaction


    The AUTH request allows to check the availability of a required amount of funds for a specific credit card and reserve it for a subsequent Settle. AUTH 3D transaction flow requires 3-D secure authorisation.   

Dev docs here.

 

Void transaction


    The VOID request is used for voiding previously performed AUTH transactions.

Dev docs here.


Settle transaction


    The Settle method is used for settling an authorized transaction that was previously performed. 

Dev docs here.