How connectors work
The Card Vault proxy sends a request you build to your payment provider, with the card data filled in from a stored card. Your servers never see the card number, and the provider's reply comes back to you unchanged. Each connector below is a recipe for one provider, written from its API reference and sent through the proxy to check that the card data lands where the provider expects it: the request to build, the placeholders to use and how to read the reply.
Every recipe uses the same endpoint, POST /cardvault/proxy on API version 1.14, and works on every plan.
Connectors
Your provider is not listed
The proxy works with any HTTPS API that takes card data in a request body. Write the request as the provider documents it and put ${ccn}, ${cvv}, ${mm}, ${yy}, ${yyyy}, ${fullName}, ${firstName}, ${lastName} or ${cardType} where the card data goes. The proxy can also sign the request (hash, HMAC or OAuth 1.0a), encrypt the body as a JWE, and present a client certificate; the API reference describes each. Tell us which provider you use at support@enigmavault.io and we will add a recipe.
See also the proxy's addresses for providers that allowlist callers, and pricing.