← Integration paths

Integration path

Web app & SaaS.

Take payments inside your web software. RESTful JSON APIs for authorization, tokenization, and reporting, plus payment links and an embeddable pay widget when you'd rather not build a checkout.

cygma.cloud/docs →Talk to us

In code

Authorize in one call.

Vault a card once, then authorize, capture, and report over REST/JSON. Tokenization keeps card data out of your stack.

  • Authorize, capture & refund
  • Tokenize for card-on-file
  • Payment links & pay widget when you’d rather not build
Read the docs →
cygma · REST
# authorize a vaulted card
POST /v2/authorize
{
  "amount": "42.50",
  "currency": "USD",
  "source": "tok_9f3ab2e1",
  "capture": true
}

# → 180 ms
{ "result": "approved", "auth_code": "T83921" }

Your toolset

Cygma and Merchant360, together.

APICygma APIAuthorization, tokenization, clearing and reporting. JSON & RESTful.VaultTokenizationVault a card once, then charge card-on-file over REST.RecurringInvoices & recurring billingSubscriptions, hosted invoices and a customer CRM with a PCI card vault.WidgetPayment links & pay widgetDrop in a hosted checkout: shareable payment links and an embeddable pay widget, no PCI scope.

Capabilities

What you can do.

Authorize & captureTokenizationCard-on-fileRecurring billingPayment linksEmbeddable widgetLevel II/III data

Approaches

Two ways to take a payment.

Build itCygma APIOne POST per transaction: sale, pre-auth and completion, refund, reversal, tokenization, Level II/III, AVS/CVV and batch settlement. JSON over HTTPS, one credential per terminal, and a cert sandbox that mirrors production.Skip the buildMerchant360For when you’d rather not build a checkout: payment links, an embeddable pay widget, hosted invoices, recurring billing, and a customer CRM with a PCI card vault. Public REST reference in preview.

Start building.

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

Read the docs →