innRoad Payments-Card Information, Decryption, and Tokens

Created by Alex Savchuk, Modified on Fri, Mar 15 at 6:53 PM by Alex Savchuk

With innRoad Payments, we handle credit card information in two ways:

  • Store the card itself
  • Or store a “token”

Generally, the only thing we can do with a stored card that we can’t do with a token is decrypt to extract the card number from innRoad. Otherwise, we support all typical functionality. Storing credit cards as tokens allows you to process payment successfully while keeping the data of your guests secure.

 

Source

What we do

Can it be decrypted?

Is it / Can it be saved as Main Payment Method?

Can it be charged later?

Can it be authorized later (and then captured)?

Can it be cancelled or refunded as normal?

  • innCenter Reservations non-EMV
  • OTA Reservations
  • We encrypt the card information and save it.
  • Card can be charged immediately or later.

 

Yes

Yes

Yes

Yes

Yes

  • Booking Engine reservation with deposit
  • EMV Device Payments
  • We charge the card
  • We convert the card to a secure token and save the token to use later.
  • We do not save the card itself.

No

Yes

Yes

Yes

Yes

  • Booking Engine reservation without deposit
  • We don’t charge the card
  • We authenticate the card (check that it is a good, valid card that can be charged)
  • We convert the card to a secure token and save the token to use later.
  • We do not save the card itself.

No

Yes

Yes

Yes

Yes

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article