Credit Card on File
A Credit Card on File is a card the customer saves once, so it can be charged later without handing over the physical card again. Only a secure token is stored. The card number stays with Datacap, and the token can only be used at your locations.
Use it for any payment that is charged after the card is first captured:
- Recurring cards — a card that is charged again on later visits or billing cycles.
- Wrist band payments — the customer's saved card is charged when their band is scanned.
- Room payments — charges are placed on the card on file for the guest's room.
- Service payments — charges for a service are placed on the saved card.
Required Item: RecurringCard
The POS needs a catalog item named RecurringCard. Saving a card works by ringing this item and running a small verification charge against the card. If the item is missing, the Add Credit Card button cannot add the order line.
Add a product with these settings (see Product & Item Catalog & Menus):
| Setting | Value |
|---|---|
| Name | RecurringCard |
| Barcode | RecurringCard |
| Price | 0.01 ($0.01) |
The barcode must be exactly RecurringCard. The Add Credit Card screen finds the item by its barcode, not by its name.
The one-cent price is the verification charge that tokenizes the card. The customer is told it is refunded immediately and that a receipt is emailed to them.
Required Service Type: PreAuth
The Add Credit Card screen rings the RecurringCard item on an order that uses a service type named PreAuth. Create it as a service type with the Sales Transaction type:
| Setting | Value |
|---|---|
| Name | PreAuth |
| Type | Sales Transaction |
The name must be exactly PreAuth. If this service type is missing, the card cannot be saved.
Prerequisites
- Datacap PayAPI is enabled. See Datacap Pay API.
- PayAPI Cards on File is turned on in Transaction Settings. See PayAPI settings.
- The RecurringCard item exists (above).
- The PreAuth service type exists (above).
- The customer has a client profile, so the token has a customer to belong to.
Saving a Card
- Open the customer's profile (Client Data) and choose Add Credit Card. A customer signed in to the app sees the same option from their own profile.
- The Save a card on file screen explains what happens: a $0.01 verification charge, a tokenized card that is never stored as a number, and a token that works at your locations only.
- Choose Add Credit Card. The RecurringCard item is added to an order and the Amount to authorize (the $0.01) is shown.
- Enter the card in the Datacap payment form and submit.
- The card is tokenized and saved to the customer. A receipt is emailed.
Accepted brands: Visa, Mastercard, Amex, and Discover.
Using a Saved Card
Once saved, the card shows as a button labeled with the brand and last four digits (for example, Visa - 1234) on the payment screen for that customer's orders.
- Staff see a Customer PIN Code field. Access to the saved cards requires the Access Card on File authorization on the staff user type, or the customer's PIN code.
- Customers signed in to the app see their own cards and can pay with them directly.
- A Remove button deletes a saved card.
For key accounts, the card entry form is not shown and the customer pays with a saved card. See Cards on File.
Quick Reference
| Item name | RecurringCard |
| Item barcode | RecurringCard |
| Item price | $0.01 |
| Service type | PreAuth (Sales Transaction) |
| What is stored | Datacap token only, never the card number |
| Verification charge | $0.01, refunded, receipt emailed |
| Used for | Recurring cards, wrist band, room, and service payments |
| Required setting | PayAPI Cards on File |