One REST API for online, phone and in-person payments, with hosted pages that keep you out of PCI scope, tokens that work across locations, and routing that fails over to a second processor.
Docs are machine-readable too: llms.txt and every page as Markdown, so coding agents can read them.
Latest v2026.10.808 · Oct 20, 2026 · 11 breaking · Changelog →# 1. Open a session for one payment (page created once, in advance) curl -X POST "$UPG_BASE_URL/api/hostedpaymentpages/sessions" \ -H "api-key: $UPG_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "hostedPageId": "{hostedPageId}", "label": "Order 1042", "amountMode": "Locked", "prefilledFields": { "base_amount": "10.00" }, "expirySeconds": 900 }' # 2. Ask for the payment link, redirect the payer to it curl "$UPG_BASE_URL/api/hostedpaymentpages/sessions/{sessionId}/payment-link" \ -H "api-key: $UPG_API_KEY" # 3. Confirm the result from the signed webhook, not the redirect
using var http = new HttpClient { BaseAddress = new Uri(baseUrl) };
http.DefaultRequestHeaders.Add("api-key", apiKey);
var res = await http.PostAsJsonAsync("/api/hostedpaymentpages/sessions", new
{
hostedPageId,
label = "Order 1042",
amountMode = "Locked",
prefilledFields = new Dictionary<string,string> { ["base_amount"] = "10.00" },
expirySeconds = 900
});
res.EnsureSuccessStatusCode();
// then GET .../sessions/{id}/payment-link and redirectWhere the card fields live decides how much you build and what you prove every year. The docs walk you through the decision.
Redirect or iframe to a branded page we serve. Typically eligible for SAQ A.
Keep your own checkout design. The card fields themselves are served by the gateway.
For phone orders and terminal apps where the card reaches your systems. Card-present reads use the same endpoint.
PCI eligibility is guidance, not a compliance determination. Confirm with your QSA or acquirer.
Sale, authorize then capture, refund, void, reversal and partial approvals. Cards, ACH, Apple Pay, 3-D Secure, Level 2/3 data, EBT fields.
Tokens instead of card numbers. Charge again with or without the customer present, and optionally share tokens across merchants under one reseller.
Customers, contracts, recurring billing runs, invoices with payable links, and a virtual terminal in the portal.
Partner platforms can assign multiple processor profiles per merchant. A rules pipeline picks one per transaction and fails over once if the first didn't process, never on an ambiguous result.
Signed event delivery as the durable record of every payment, built to be verified and safely replayed.
Resellers, private-label branding, merchants, roles, audit log, reports, surcharging with per-state rules, and rate limits reported in headers.
The sandbox processor answers from a fixed table, so every case is repeatable: declines, AVS and CVV results, partial approvals, ACH returns, processor latency and failover.
# Blueprints in the docs
accept-your-first-payment
authorize-now-capture-later
save-a-card-and-charge-it-later
bill-a-customer-on-a-schedule
invoice-a-customer-and-get-paid
retry-a-payment-safely
exercise-processor-failover
simulate-a-card-decline
simulate-an-ach-return
trigger-a-partial-approvaluLite POS and uLite Online run on UP Gateways in production—powering in-person terminals, mobile POS and online ordering for restaurant and retail businesses across the U.S.
Cloud-based terminal, mobile POS and 24/7 multilingual AI phone ordering built on UP Gateways. ulite.com
Commission-free online ordering on the restaurant's own site, processing online payments through UP Gateways. uliteonline.com
Acquiring, merchant processing and 24/7 multilingual client support nationwide. letsgoup.com
Cardholder data encrypted with AES-256-GCM under a managed key vault; primary account numbers masked wherever displayed.
CVV, PINs and full magnetic stripe or chip data are never stored.
PCI DSS v4.0 compliant gateway: cardholder data handled to the v4.0 standard. Security details →
Security, privacy, terms, subprocessors and compliance materials published at docs.upgateways.com.
Request sandbox credentials and connect with our integrations team.