isCreditCard

Summary

Sails provides the isCreditCard validation rule to verify whether a string is a valid credit card number. However, your application must be PCI compliant before storing credit card details. Instead, consider using third-party payment processors like Stripe or Paystack for handling payments securely.

Example: Validating a Credit Card Number

To enforce this rule in a Sails model, define the attribute as follows:

creditCard: {
  type: 'string',
  isCreditCard: true
}

Key Takeaways:

Only store credit card numbers if your app is PCI compliant.
Supports different formats (with/without spaces or hyphens).
Validation ensures exactly 16 digits.
Use third-party services like Stripe or Paystack instead.

Testing the Validation Rule

Invalid Credit Card

await User.create({ creditCard: "123456789" });

❌ Fails validation because it’s too short.

Valid Credit Card

await User.create({ creditCard: "4111111111111111" });

✅ Passes validation.

Valid Credit Card with Spaces

await User.create({ creditCard: "4111 1111 1111 1111" });

✅ Passes (spaces are ignored).

Valid Credit Card with Hyphens

await User.create({ creditCard: "4111-1111-1111-1111" });

✅ Passes (hyphens are ignored).

Transcript

Now let’s look at another validation rule—the one for credit card numbers.

🚨 Quick Warning:
If your app is not PCI compliant, DO NOT store credit card numbers. Instead, use services like Stripe or Paystack for secure payment handling.

However, if your system is PCI compliant and you need to store credit card details, Sails provides a validation rule to check if the number entered is a valid credit card number.

Defining a Credit Card Attribute in Sails

To add credit card validation to our model, we define an attribute like this:

creditCard: {
  type: 'string',
  isCreditCard: true
}

Testing Credit Card Validation

Let’s test this in Guppy.

1. First, let’s try an invalid credit card:

await User.create({ creditCard: "123456789" });

Fails, because a valid credit card should have 16 digits.

2. Now, let’s try a correct 16-digit number:

await User.create({ creditCard: "4111111111111111" });

Passes, because it’s a valid format.

3. What about a credit card with spaces?

await User.create({ creditCard: "4111 1111 1111 1111" });

Still passes. The validation ignores spaces.

4. What about a credit card with hyphens?

await User.create({ creditCard: "4111-1111-1111-1111" });

Also passes, because hyphens are ignored too.

Final thoughts

The isCreditCard rule ensures the correct structure of a credit card number.
Do not store credit card numbers unless PCI compliant.
Prefer third-party payment processors like Stripe or Paystack for handling payments securely.

Locked video