payments/sdk. Obtain the matching Payments source checkout from your Rach contact and install its directories. These instructions do not assert that a package is published to npm, PyPI, a Go repository or pub.dev.
Install
https://api.rach.finance; SDK paths already include /api/v1. Override the base origin only for your trusted test deployment. Keep merchant API keys on your backend. A shipped Flutter app or browser uses a session created by that backend and the public snapshot/widget.
Create on your backend
Node
The Go
AmountExact input serializes as the wire amount string. Legacy numeric inputs remain accepted. Response amount_exact is requested; charged_amount_exact is actual verified settlement when available. Do not replace either with a binary floating-point value in your accounting records. All clients use POST for verify-now and preserve is_test_mode returned by the backend.
Public Flutter snapshot
sdk.js widget are different interfaces.
Activation
Activation does not create a JWT, approve KYC or enable live payments. Existing accounts confirm their current password and TOTP when required. Sign in normally afterward. Public self-registration is disabled.
Webhook verification
JavaScript exposesRachFinance.verifyWebhook(rawBody,signature,secret) for Node.js. Python and Go can use their standard HMAC libraries; verification examples use the exact raw body and fail closed on malformed signatures.
Verify, durably deduplicate event_id, then fulfill in your backend transaction. Do not put a webhook secret into a mobile/browser verifier or treat widget success as financial confirmation.
