import DyScan
in the file with the view controller that will instantiate DyScan. Unlike card.io, a bridging header is not necessary as DyScan is written in Swift.onFailure(_ paymentViewController: DyScanViewController!, reason: DyScanExitReason)
, and onSuccess(_ cardInfo:DyScanCreditCardInfo!, in paymentViewController: DyScanViewController!)
. These should be analogous to the corresponding functions with Card.io, except that the names have been modified and the failure case provides a reason that you may choose to use to give a more robust experience.DyScanViewControllerDelegate
instead of CardIOPaymentViewControllerDelegate
.CardIOPaymentViewController
with DyScanCreditCardInfo
is analogous to card.io's, but contains fewer methods. You can access the relevant fields by indexing cardNumber
, expiryMonth
, and expiryYear
.import DyScan
in the file with the view controller that will instantiate DyScan. Unlike card.io, a bridging header is not necessary as DyScan is written in Swift.onSuccess(_ dyScanIOView: DyScanView!, didScanCard cardInfo: DyScanCreditCardInfo?)
, and onFailure(_ dyScanIOView: DyScanView!, reason: DyScanExitReason)
. These should be analogous to the corresponding functions with Card.io, except that the names have been modified and the failure case provides a reason that you may choose to use to give a more robust experience.DyScanViewDelegate
instead of CardIOViewControllerDelegate
.CardIOViewController
with DyScanCreditCardInfo
is analogous to card.io's, but contains fewer methods. You can access the relevant fields by indexing cardNumber
, expiryMonth
, and expiryYear
.