Skip to content
Torvexx

Developers

Integrate in an afternoon.Run it for years.

A REST API, four SDKs (JavaScript, Python, PHP, Ruby), signed webhooks and a test mode to try every state of a payment before going live.

1 · Create a paymentshell
curl https://api.torvexx.com/v1/payments \
  -u "$TORVEXX_SECRET_KEY:" \
  -H "Idempotency-Key: 8f1c2e60-order-1042" \
  -d amount=24800 \
  -d currency=usd \
  -d customer=cus_4MR8 \
  -d "metadata[order_id]=1042"
Responsejson
{
  "id": "pay_7Q2C",
  "object": "payment",
  "amount": 24800,
  "currency": "usd",
  "status": "created",
  "checkout_url": "https://pay.torvexx.com/c/pay_7Q2C"
}
2 · Receive the outcomenode.js
import express from "express";
import { verifySignature } from "./torvexx"; // provided with your SDK

app.post("/webhooks/torvexx", express.raw({ type: "application/json" }), (req, res) => {
  const event = verifySignature(req.body, req.header("Torvexx-Signature"), process.env.TORVEXX_WEBHOOK_SECRET);
  res.sendStatus(200);                      // acknowledge first

  if (event.type === "payment.captured") {
    queue.add("fulfil-order", event.data);  // then work asynchronously
  }
});

Illustrative example. Exact endpoints, keys and SDK packages are provided with your sandbox access.

01

Getting started

Once your application is approved you receive sandbox credentials: a secret key for your server and a publishable key for the browser. Every request is authenticated with the secret key over HTTPS; never expose it client-side.

  • Request sandbox access from your account manager
  • Store the secret key in your server environment
  • Create a test payment and follow it in the dashboard

02

API reference

Resources follow the life of a payment. Each object carries a status that moves forward only, and an idempotency key on every write request makes retries safe.

  • payments: create, capture, refund, retrieve
  • customers: profiles linked to their payments
  • disputes: status, deadline, evidence submission
  • payouts: schedule, statement, included transactions

03

SDKs and plugins

Libraries for four languages and 25+ platform integrations. Installation details are shared with approved merchants together with their credentials, so you always install the version that matches your account.

  • SDKs: JavaScript, Python, PHP, Ruby
  • Plugins for Shopify, WooCommerce, PrestaShop, Magento, BigCommerce
  • Payment links with no code at all
  • REST API for any system that can make an HTTPS request

04

Guides

Step-by-step walkthroughs for the integrations merchants ask about most.

  • Hosted checkout in a few lines
  • Embedded payment form
  • Recurring payments and failed-charge follow-ups
  • Multi-currency pricing
  • Responding to a dispute

05

Webhooks

Subscribe to the events you care about. Each delivery is signed; verify the signature before acting, respond with a 2xx quickly, and process the event asynchronously. Failed deliveries are retried.

  • payment.authorized, payment.captured, payment.failed
  • dispute.opened, dispute.closed
  • payout.sent
  • customer.updated

06

Best practices

A few habits that keep an integration reliable.

  • Use idempotency keys on every write
  • Treat webhooks as the source of truth for status
  • Never log full card data or secret keys
  • Test failures and 3-D Secure challenges in sandbox
  • Rotate keys when a team member leaves

Stuck on an integration?

Send us the request ID and what you expected to happen. We answer by email within 24 hours.

Contact the team