Card Processing and Financial Infrastructure - with the crypto world in mind
- Tweets 110
- Following 744
- Followers 27
- Likes 12
Endpoint down for a deploy? Rigid webhooks are signed with HMAC-SHA256, with secret rotation built in. Failed deliveries retry at 1m, 5m, 30m, 2h and 24h, and any event can be redelivered with one click from the console. rigid.fi/developers
1
47
Card issuing has three roles. The programme manager owns the product, cardholders and first-line risk. The issuer or sponsor holds the licence and scheme membership. The processor runs authorization, clearing, the ledger and disputes. That's Rigid. rigid.fi/card-issuing-adviso…
1
23
From tap to balanced books in one pass. The network routes the authorization to Rigid, card state, controls, velocity and funding are checked together, Fraud AI scores it in 18ms, the double entry posts and a signed webhook reaches your systems. Same transaction, no batch.
1
11
Our API reference and the machine-readable OpenAPI spec are generated from the same contract the platform is built against, so the docs and the API can't disagree. Plain REST over HTTPS, bearer tokens, idempotency keys, JSON. Start here rigid.fi/docs
1
19
Not every buyer is a person. A car paying for its own charge, a device buying data, a workload buying compute.
On Rigid, each can get a virtual card under a signed mandate a human set, with a cap, budget and expiry checked at authorization, plus a ledger entry per purchase.
1
18
Adding credit or BNPL next to a debit card shouldn't need a second stack.
On Rigid, debit, prepaid and credit account ranges on Visa and Mastercard run on the same rails, with Fraud AI that sees the whole programme, not one card at a time.
rigid.fi/platform
13
Switching card processors doesn't have to be one big cutover. In Rigid's gateway mode your core keeps the ledger and the approve or decline logic, while Rigid takes over the network side. Swap that first, move the books later, or never. rigid.fi/gateway
1
8
Making an insurance or warranty claim? Picture the payout as a virtual card that only works at repair shops, capped at the claim amount. You get the fix paid, the insurer gets a charge it can match to the claim. Card programmes running on Rigid can create cards like that by API.
7
New card product, new market, new rules. On Rigid, that is configuration, never a reissuing project. Programmes are native objects you run from one console and one API, with organisations keeping teams apart, scoped roles and a tamper-evident audit trail. rigid.fi/platform
12
Three calls from zero to a first card. POST /v1/oauth/token, POST /v1/cardholders, POST /v1/cards. Plain REST with bearer tokens and Idempotency-Key, no client library required and nothing to keep up to date. A fourth, POST /v1/simulated-spends, runs a test authorization. rigid.fi/developers
1
11