All systems operational

Encrypt. Tokenize. Ship anywhere.

One production-ready JSON API for payment encryption, browser fingerprinting, proof-of-work and challenge solving. Eleven gateways, zero client-side crypto.

Read the docs

0 Providers

0 HTTP verbs

JSON Response

0 Uptime

/

No endpoints match

Try a different keyword or clear the filters.

60-second setup

Quickstart

Every endpoint accepts GET query parameters or a POST JSON body and returns a single JSON object.

Your base URL /

1 · Authenticate nothing

No API keys for the encryptors — you supply the gateway public key per request.

{ "kty": "RSA", "n": "YOUR_MODULUS", "e": "AQAB" }

2 · Send a request

Pick an endpoint and POST the card fields with the provider key.

curl -X POST "https://your-host/encrypt/cybersource" \
  -H "Content-Type: application/json" \
  -d '{"card":"4111111111111111","cvv":"123","month":"12","year":"2025","key":{...}}'

3 · Read the response

Encrypted payloads come back under encryptedData (or gateway-specific fields).

{
  "status": true,
  "encryptedData": "…",
  "method": "POST",
  "timestamp": "2025-06-16T10:30:00.000Z"
}

Contract

Response & errors

Consistent envelopes keep integration simple across all gateways.

Success

HTTP 200 with a JSON body.

{
  "status": true,
  "encryptedData": "…",
  "method": "POST",
  "timestamp": "2025-06-16T10:30:00.000Z"
}

Errors

HTTP 400 for bad input, 500 for encryption failures.

{
  "status": false,
  "error_message": "Required field `card` is missing."
}

Status	Meaning	When
200	OK	Encryption / solve succeeded
400	Bad Request	A required field is missing or invalid
429	Rate limited	More than the per-IP window (100 / 15 min in prod)
500	Server error	Gateway rejected the request or encryption failed