CCVALID
This help page is for Studio. This information is also available for Desktop Studio.
|
Checks that a credit card has valid digits and a valid expiration date. |
Dependencies
- Ccvalid does not verify that a particular credit card number exists; it simply ensures that a number could exist using the MOD-10 checksum algorithm.
- This action can validate credit card numbers with up to 16 digits. It rejects all numbers with more than this number digits, whether they are valid or not.
- Ccvalid does not run a charge on a credit card; it only validates that the number could be valid.
Supported Script Types
|
|
|
|
|
|
|
|
Generic |
Chat | Phone | Voicemail | Work Item | SMS | Digital |
Input Properties
These properties define data that the action uses when executing.
Property |
Description |
---|---|
Add Caption |
Enter a short phrase that uniquely identifies this action in the script. The caption appears on the script canvas under the action icon. |
Credit Card | Tthe sequence of digits that make up the credit card number. |
Expire Month | Thea card's month of expiration. This must be entered as a two digit number, such as 02 for February. |
Expire Year | The card's year of expiration. This must be entered as a four digit number, such as 2030. |
Validate Luhn |
When enabled, the action validates that credit card numbers are entered correctly. It uses the Luhn algorithm to do the validation. This does not check that the numbers are correct. In Value Mode: Click to Off to disable the validation of credit card numbers. Leave set to On to have credit card numbers validated. In Expression Mode: Enter false to disable the validation of credit card numbers. Leave set to true to have credit card numbers validated.
|
Validate CC Type |
Validates the type of credit card.
In Value Mode: Click to Off to disable the validation of credit card type. Leave set to On to have credit card types validated. In Expression Mode: Enter false to disable the validation of credit card numbers. Leave set to true to have credit card numbers validated.
|
Result Branch Conditions
Result branch conditions allow you to create branches in your script to handle different outcomes when an action executes.
Condition |
Description |
---|---|
Default | Path taken unless the script meets a condition that requires it to take one of the other branches. It is also taken if the action's other branches are not defined. |
Valid | Path taken if the card number passes the MOD-10 checksum algorithm and the month/year parameters are valid entries greater than or equal to today's date. |
BadCard | Path taken if the card number fails the MOD-10 check. |
BadExpireDate | Path taken if the expiration date is either too old or invalid. |