Skip to main content
Each environment ships as one artifact: rinne-sdk-checkout-sandbox and rinne-sdk-checkout-production, released on the same version. Pin the version named in your beta access email, and upgrade when Rinne announces a version as live.
​
Current sandbox release
The sandbox release available today. It contains:
  • One dependency: rinne-sdk-checkout-sandbox brings the rest of the SDK with it.
  • The managed checkout, launched through Checkout.Contract, with the preparing, tap, processing, PIN, approved, declined, failed and cancelled screens in English and Brazilian Portuguese.
  • CheckoutConfig with ten fields that theme the screens and the certified PIN pad together.
  • PaymentResult with Approved, Declined, Failed and Cancelled, and the thirteen-value ErrorCode with ErrorCatalog.
  • Card-present refunds by re-tap with type = REFUND.
  • AntennaSetup, the Nfc helpers and Payments.checkDeviceReadiness.
  • Terminal preparation with a backend-minted access token and Environment selection.
Alpha releases may rename or remove public API between versions. Each breaking change is called out here when it ships.

​
How releases work

A release is a version bump on the SDK repository; the registry serves every published version, and a version stays available after newer ones ship. During the closed beta only the sandbox artifact is published; Rinne provides the production artifact when your integration is approved for launch. A new card-reader version inside the SDK needs its card configuration published on Rinne’s side before devices on it can prepare a terminal. Rinne does this before announcing a version, which is why upgrading only to announced versions matters: a build on an unannounced version fails at getReady with EMV_CONFIG_UNAVAILABLE.