DEVELOPER PLATFORM
Changelog
El RapidCents changelog records Versión de API history, new endpoints, behaviour changes y obsolescencia programada notices con su migration windows. Two kinds de entry appear y they demand different reactions: additive changes reach usted sin action because un pinned version keeps behaving as documented, while breaking changes ship behind un new version y stay optional until usted move. Each entry names qué changed, que version carries it, whether it es additive o breaking, y para un obsolescencia programada el date el old behaviour stops.
- Entorno de pruebas (sandbox) con documented test tarjetas
- Signed webhooks
- Typed errors y idempotent retries
- Dedicated developer support
Qué crosses el wire
Qué un entry tells usted
Qué changed, que Versión de API carries it, whether it es additive o breaking, y para un obsolescencia programada el date el old behaviour stops. Anything ese requires action says so explicitly rather than leaving usted a infer it.
Qué su cuenta carries
UN pinned Versión de API, sent en cada request o defaulted per cuenta. Ese pin es qué decides que entries en el changelog apply a usted today y que describe un future usted have no opted into.
Qué un migration involves
Point un entorno de pruebas (sandbox) client en el new version, run su regression suite, compare el response shapes el changelog flagged, then move production. El old version keeps serving until el window closes.
Cuando a use it
Planning maintenance
Check para deprecations antes de each release cycle rather than después de un incident, y give el migration un ticket while el window es still comfortable.
Debugging a behaviour change
Confirm whether un observed difference fue un intentional, documented change antes de spending un afternoon looking para un bug en su own code.
Reviewing a dependency upgrade
Un SDK release targets un specific Versión de API, so bumping el package puede move usted across un boundary el changelog already described.
Cómo a implement Changelog
Subscribe a el changelog antes de going live, into un channel someone actually reads.
Pin su Versión de API explicitly rather than tracking latest.
Record que version each service sends, so un upgrade es un known set de deployments.
Test el new version en entorno de pruebas (sandbox) during el obsolescencia programada window, no en el end de it.
Upgrade one service en un time y confirm against su own regression suite.
Qué fails, y cómo usted find out
Tracking latest instead de pinning
Un unpinned integration inherits cada change en el day it ships, including el ones usted would have wanted a schedule. El symptom es un response shape ese moved con no deploy en su side.
El obsolescencia programada window closing quietly
Notices son published, but un suscripción pointed en un unmonitored inbox es el same as no suscripción. Route changelog entries somewhere el en-call rotation puede see them.
Different services en different versions
One codebase pinned a two versions produces behaviour ese depends en que service handled el request. Inventory el pins antes de un migration, no during one.
Upgrading everything en once
UN single deployment ese moves cada service across un version boundary has no partial reversión de despliegue. Move one, watch it, then move el next.
Sandbox versus production
New versions son testable antes de usted commit
UN entorno de pruebas (sandbox) client puede ser pointed en el new Versión de API while production stays pinned, so el migration es validated against su own code rather than against release notes.
Entorno de pruebas (sandbox) es dónde un obsolescencia programada es cheap
Running el old y new versions side por side en entorno de pruebas (sandbox) shows exactly que de su assertions change, que es el list un migration ticket should contain.
Version pinning behaves identically
El pin es honoured el same way en both environments, so un entorno de pruebas (sandbox) run genuinely represents qué el production upgrade will do.
Questions about Changelog
Cómo much notice es given antes de un breaking API change?
Breaking changes ship behind un new version con un published obsolescencia programada window, so integrations pinned a el previous version keep working while usted migrate.
Am I upgraded automatically?
No. Versions son pinned per cuenta, so un upgrade es un explicit action usted take después de testing.
Dónde son seguridad fixes announced?
Non-breaking seguridad fixes son applied immediately y recorded en el changelog; anything requiring su action es communicated directly.
Qué counts as un cambio incompatible con versiones anteriores?
Anything un existing integration could reasonably ser relying en: un removed o renamed field, un narrowed type, un new required input, o un status ese starts being returned dónde it previously fue no. Added optional fields y new endpoints son no breaking.
Qué happens if I never migrate off un deprecated version?
It keeps serving until el published window closes, y el notice states ese date. Después de it closes, requests pinned a it stop being served, que es why el window es announced rather than el removal.
Cómo do I find out que version my integration es actually sending?
Desde su own request logs, no desde un assumption. Services configured en different times drift apart, y el pin one team documented es often no el pin another team deployed.
Does an SDK upgrade change my API version?
It puede. Each SDK release targets un specific Versión de API, so read el SDK release notes alongside el changelog entry y treat el pair as one migration rather than two unrelated bumps.
Cómo do I migrate a un new Versión de API safely?
Point un entorno de pruebas (sandbox) client en el new version while production stays pinned, run su regression suite, compare el response shapes el entry flagged, then move one service en un time. El old version keeps serving until el window closes, so there es no reason a move everything en un single deploy.
Dónde should changelog entries ser delivered?
Into un channel el en-call rotation actually reads. UN suscripción pointed en un unmonitored inbox es el same as no suscripción, y un obsolescencia programada window closing quietly es qué produces un response shape ese moved con no deploy en su side.
Continue el integration
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 request y…
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 helpers.
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
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
