finds.dev← search

// the find

sbycrosz/react-native-credit-card-input

★ 1,507 · TypeScript · MIT · updated Nov 2025

Easy, cross-platform credit-card input for your React Native Project! Start accepting payment 💰 in your app today!

A TypeScript rewrite of the long-dormant react-native-credit-card-input, giving you a skeuomorphic card UI plus a compact 'lite' variant for collecting card number, expiry, and CVC on iOS, Android, and web. Aimed at people who want a quick, good-looking card form or a proof of concept, not teams building a serious payment flow.

Actively maintained with real tests for all three components (CreditCardInput, LiteCreditCardInput, CardView) and a CI workflow, which most small RN UI libs skip entirely. Ships three usable pieces — full input, compact input, and a standalone CardView — so you can reuse the card visualization without the form logic. Works cross-platform (including web) from one codebase, and onChange gives you sanitized values, per-field status, and detected issuer type in a single callback instead of you wiring that up. The README is unusually candid for a project with this name — it tells you to just use react-hook-form + card-validator instead if you need real validation, rather than overselling itself.

No mention anywhere of New Architecture (Fabric)/bridgeless support, which is the default for new RN projects at this point — worth checking before adopting, since old-arch-only components are an increasingly dead end. Customization is limited to style/font/image props on a fixed skeuomorphic card layout; there's no headless mode, so it clashes with any design system that wants a different visual language for the card face. The docs never explain what backs the 'valid'/'invalid' status — whether card numbers get an actual Luhn checksum or just prefix/length formatting — which is exactly the detail you want to know before trusting it on a payment form. It's purely a UI layer with no discussion of where the raw card number lives in memory or how you're supposed to hand it off for tokenization, which someone new to payment integrations could easily miss.

View on GitHub →

// want more like this?

We dig through GitHub every week and send a few repos picked for what you actually care about — each with an honest take like this one.

Get finds in your inbox → Search again →