Some card acquirers support a card verification operation. The operation checks the validity of a stored card without making an actual authorization on the card. That is, the check will not be visible to the cardholder on their bank statement. Currently this operation is only supported for acquirer Nets, Swedbank, Bambora and Valitor. Notice that this operation is subject to charges. See frisbii.com for the current pricing or contact contact@frisbii.com for more information on pricing and how to utilize this service.

To test the operation with the test acquirer, specific CVV codes can be used to trigger erros:

CVV	State	Error
`901`	`soft_declined`	`insuffcient_funds`
`902`	`hard_declined`	`declined_by_acquirer`
`903`	`processing_error`	`acquirer_error`

Errors

The operation can generate the following errors beside the generic HTTP error codes described here.

Error code	HTTP code	Description
`40`	`404`	Payment method not found
`18`	`404`	Card not found
`138`	`400`	Card verification not supported by the current acquirer agreements

200Successful operation

400Invalid request, see error codes at https://api.frisbii.com/v1/error_codes

401None or invalid credentials provided in access to secured resource

403Not authorized to perform resource operation

404Resource or referenced resource not found, see error codes at https://api.frisbii.com/v1/error_codes

429Request limiting exceeded, request rate or concurrent requests, see error code 122 and 123

500Internal service error, error is reported automatically to Frisbii