Sending a Card Validation

Before sending a Card Push Transfer, you confirm with the issuing bank that the recipient's card number is valid and that the name and address of the cardholder match what they've provided you. You do this by creating a Card Token for the card and then creating a Card Validation, a $0 network message sent to the issuer. Since push-to-card transfers are non-reversible it is crucial to validate that you are pushing funds to the expected cardholder to prevent fraud.

Card Validations

Card Validations are $0 account verifications sent to the card network that are used to verify the validity of a given card number. They also let you validate the cardholder’s information, such as their name and their address. Since push-to-card transfers are non-reversible it is crucial to validate that you are pushing funds to the expected cardholder to prevent fraud.

Similar to other Increase APIs, the Card Validation creation endpoint creates a Card Validation that then moves through an asynchronous state machine. To retrieve the outcome of a Card Validation you can either use the Card Validation retrieval endpoint or listen for card_validation.created webhooks.

Lifecycle

pending_submission	The validation is queued to be submitted to the card network.
submitted	The validation has been submitted and is pending a response from the card network.
complete	The validation has been sent successfully and is complete.
declined	The validation was declined by the network or the recipient's bank.
requires_attention	A rare status set when a validation needs manual intervention from the Increase team. More about requires_attention.

Once a Card Validation is complete and confirms the cardholder, you can send a Card Push Transfer to the card.