Second pass for the lib about gringotts HOT 2 CLOSED

On task 3

I honestly don't know what ActiveMerchant's cacert.pm is doing in their repo (seems to be used here reasonably). This is Mozilla's CA bundle, which is available on literally every OS via the system's ssl module. Browsers "trust" CAs that feature in this list. All good HTTP(S) client libs will use the system's certificates to make https requests right out of the box. Like python's requests library.

Client side SSL

This answer on SO helps.
Some gateways require/allow a client (ie, a merchant) to authenticate itself using a Client-Side SSL Certificate instead of using an API token or other popular methods. For such gateways, we need to send this client cert in the request.

HTTPoison uses hackney and any SSL options passed to HTTPoison/hackney fall through to Erlang's SSL module. So, to send a client cert via HTTPoison, just pass the required SSL options cert or certfile as documented.

Server side SSL

A gateway who's SSL cert is not trusted by Mozilla's CA shouldn't won't exist, so we'll never have to use the cacerts or cacertfile options. Which makes me wonder why AM keeps the PEM in the repo...

TL;DR

Maybe need a helper for a gateway that allows/requires client side SSL verification as an authentication mechanism. List of such gateways supported by AM, we have encountered none so far.

from gringotts.

Closing this as we do not see any way to provide some common helpers to make connections. Vanilla HTTPoison` is best.

from gringotts.