DEVELOPER PLATFORM
Build connected pago experiences con RapidCents
RapidCents es una plataforma de pagos software teams integrate mediante REST APIs, signed webhooks, Rapid.js campos de pago alojados, SDKs y un entorno de pruebas (sandbox) con documented test tarjetas. Terminal, proceso de pago, pago-link y API pagos land en el same cuenta de comerciante, so reporting, reembolsos y liquidación stay one integration.
- Entorno de pruebas (sandbox) con test tarjetas
- Signed webhooks
- Node y Python SDKs
- Dedicated developer support
Try it, edit values and click buttons
API request
POST /v1/payments
{
"amount": 24900,
"currency": "USD",
"capture": true,
"metadata": { "order_id": "4821" }
}Response
Click "Send request" to see the API response
Processing payment…
201 Created
{ "id": "pay_7xK2m", "status": "approved", "amount": 24900 }Demonstration data only
Quickstart
UN RapidCents integration starts en entorno de pruebas (sandbox): obtain test credentials, create un pago con documented test tarjetas, verify webhook (notificación HTTP) signatures, then move a production después de un integration review.
1. Obtain credentials
Request sandbox access.
2. Create test pago
Use documented test tarjetas.
3. Receive webhook
Verify signatures.
4. Go production
Guided migration.
Developer resources
Developer Recursos en RapidCents cover el API, webhooks, Rapid.js, plugins, entorno de pruebas (sandbox), RapidBridge y el guides para connecting existing software sin un second acquiring relationship.

RapidCents developer docs open on a workstation: API reference, a copy-ready example, and a terminal for the in-person path. Documentation
Complete developer documentation para RapidCents pago APIs, webhooks…
Explore
The RapidCents quickstart path: create a test payment, see the response, and confirm it on a sandbox terminal. Quickstart
Get entorno de pruebas (sandbox) credentials, create un test pago, receive un webhook (notificación HTTP) y prepare…
Explore
The RapidCents API reference on a workstation, with a sample request, the matching response, and a test terminal. API Reference
REST endpoints para pagos, clientes, reembolsos, webhooks y settlements con…
Explore
A RapidCents SDK project running a test payment, with the same sale visible on a sandbox terminal. SDKs
Official SDKs para Node.js, Python, PHP y mobile con typed models y retry…
Explore
A RapidCents webhook delivery timeline next to the payment that triggered it, with a test terminal on the desk. Webhooks
Signed webhook (notificación HTTP) events para pago lifecycle con idempotent procesamiento guidance.
Explore
A RapidCents server-to-server request being signed on a developer desk, with a sandbox terminal for the in-person counterpart. Authentication
API keys, OAuth para partners y request signing para server-a-server…
Explore
A typed RapidCents API error on screen, next to the declined sandbox terminal sale that produced it. Errors
Typed error codes, retry guidance y idempotencia patterns para production…
Explore
RapidCents sandbox testing: documented test cards, a simulated decline, and a terminal for the in-person cases. Testing
Tarjeta de prueba numbers, simulated declines y entorno de pruebas (sandbox) liquidación events.
Explore
A RapidCents sandbox merchant account running test payments, isolated from production, with a sandbox terminal on the desk. Entorno de pruebas (sandbox)
Request entorno de pruebas (sandbox) access con test comerciante IDs y isolated environment.
Explore
A developer working through a RapidCents integration guide, sandbox terminal on the desk and a successful test result on screen. Integration Guides
Step-por-step guides para comercio electrónico, POS, mobile y mercado en línea (marketplace) integrations.
Explore
A copy-ready RapidCents payment example next to the sandbox response it produces. Code Samples
Copy-ready examples para pago creation, captura, reembolso y webhook (notificación HTTP)…
Explore
The RapidCents API changelog open beside a sandbox result and a test terminal, showing what changed in the latest release. Changelog
Versión de API history, breaking changes y obsolescencia programada notices.
Explore
RapidCents platform status and incident history on a workstation, so an integrator can see whether the rails are up. System Status
Real-time platform status, incident history y subscribe-a-updates.
Explore
A RapidCents developer-support desk tracing a live payment request beside the merchant dashboard and a test terminal. Developer Support
Developer Soporte channel con SLA tiers para production integrations.
Explore
A RapidCents API request and its response on a developer workstation, with the merchant dashboard and a test terminal. RapidCents APIs
REST APIs para pagos, reembolsos, clientes, tokens y liquidación, con…
Explore
Rapid.js hosted card fields on a developer workstation, keeping card entry out of the merchant's PCI scope. Rapid.js
Embedded pago components para el web ese keep tarjeta entry inside…
Explore
An unpaid invoice open in a third-party CRM with the RapidBridge panel beside it, showing the record number, amount, customer and email it detected from the page on its own, and buttons to send a payment link or charge a saved card. RapidBridge
Automatic pago detection en 178 comercio applications: RapidBridge takes…
Explore
A RapidCents plugin connecting a commerce admin to checkout, so card payments work without custom gateway code. Plugins & Extensions
UN WooCommerce pasarela de pagos, un Shopify connection y prebuilt integrations…
Explore
RapidCents connected to accounting and operations tools a business already runs, with payments landing in the same dashboard. Third-Party Integrations
Connect RapidCents a accounting, CRM, booking y operations tools su…
Explore
The RapidCents tokenization API returning a card token, so merchant software never stores the PAN. Tokenization API
Create, reuse y retire pago tokens programmatically so su systems never…
Explore
A RapidCents subscription charge created over the API, using the same billing engine as the dashboard. Recurring Pagos API
Build subscriptions, installments y retry logic against el same billing…
Explore
The RapidCents account-updater API applying refreshed card credentials so a stored token survives a reissue. Servicio de actualización de tarjetas API
Query y apply refreshed tarjeta credentials so stored tokens keep working…
Explore
APPIE interoperability on a RapidCents desk: a terminal and host path that can work across processor boundaries. APPIE™
Pago interoperabilidad infrastructure ese lets terminals y hosts work…
Explore
APPIE at the terminal layer: processor interoperability without swapping the RapidCents hardware estate. APPIE en Terminal
Enable processor interoperabilidad en la terminal layer, sin replacing el…
Explore
APPIE at the host layer, routing RapidCents platform traffic across more than one processor. APPIE en Host
Enable pago interoperabilidad en el host layer para platforms routing across…
Explore
Take the next step
Talk a un RapidCents specialist
RapidCents Análisis de comisiones reads un estado de cuenta de procesamiento y shows intercambio interbancario separately desde el markup. Upload un estado de cuenta para un instant breakdown, o open una cuenta de comerciante y start accepting pagos en one cuenta.
- No obligation
- Payment specialists, not a call centre
- Secure statement upload
Preguntas frecuentes
Cómo do I get API credentials?
Desde el panel de control del comercio, once la cuenta es approved. Entorno de pruebas (sandbox) credentials son issued separately desde production ones y work solo against test data. El Developer Términos set out dónde each kind de key may live — un clave secreta en un server usted control, never en un navegador o un app bundle.
Puede I take tarjetas en my own proceso de pago sin expanding my PCI scope?
Yes, con Rapid.js campos de pago alojados o el página de pago alojada: la tarjeta es posted desde el cliente’s navegador a RapidCents y never touches su server, que keeps usted en SAQ UN. Relaying la tarjeta mediante su own server moves usted a SAQ D. El PCI Compliance page y el Developer Términos both explain el line.
Son webhooks delivered más than once?
They puede ser. Delivery es en least once, so verify el signature con su webhook (notificación HTTP) secret y record el identificador de evento so un redelivery es recognised rather than processed twice. El webhooks documentation lists el events y el signature scheme.
Es there un status page y un obsolescencia programada policy?
Yes. El status page under /Desarrolladores reports platform availability, y el Developer Términos state el notice period antes de un Versión de API es retired y cómo it es announced.





