← Integration paths

Integration path

E-commerce.

Card-not-present acceptance online, with vaulted customers and multi-currency reach. Hosted pages and fields keep card data off your servers, and Handpoint's European e-commerce suite extends acceptance across the Atlantic.

e-commerce API docs →Talk to us

In code

Charge card-not-present.

Card-not-present acceptance with vaulted customers and hosted fields, including the European e-commerce suite, with no card data touching your servers.

  • Hosted fields & hosted checkout
  • Vaulted customers & card-on-file
  • Apple Pay, Google Pay & APMs
Read the docs →
cygma · REST
# charge a card-on-file customer
POST /v2/charges
{
  "amount": "89.00",
  "customer": "cus_7Kd2",
  "entry_mode": "ecommerce",
  "descriptor": "ACME * ORDER 5567"
}

Your toolset

Cygma and Merchant360, together.

HostedPayment page & fieldsMerchant360 hosted checkout and an embeddable pay widget keep card data off your servers.APICNP authorization & tokenizationCygma authorizes card-not-present sales and tokenizes cards for card-on-file over JSON and HTTPS.VaultVaulted customersA PCI card vault stores customers so charges and recurring billing run without holding card data.LinksPayment linksShare a secure payment link and get paid, with no integration required.

Capabilities

What you can do.

Hosted payment pageHosted fieldsPay-by-linkApple Pay & Google PayAlternative payment methodsMulti-currencyCheckStatus verification

Two ways to build

Card-not-present, done right.

1Cygma APIAuthorize mail-order and e-commerce sales with ECI, AVS and CVV2 verification. Tokenize cards for card-on-file, then issue refunds and reversals. JSON over HTTPS, with a certification sandbox that mirrors production. Read the docs →
2Merchant360, no buildTake payments without writing an integration: a hosted pay page, an embeddable pay widget, and shareable payment links. Store customers in a PCI card vault and run recurring billing. Explore Merchant360 →
3Off your serversVaulted customers keep card data off your servers and out of PCI scope, so charges and card-on-file run against a token instead of a card number.

Start building.

Read the docs, or talk through your integration and revenue model with the team.

Read the docs →