Through Datacap’s NETePay Hosted™ platform, merchants can take advantage of processor-agnostic omnichannel tokens. Tokens are used to pair a customer with their payment information without requiring access to the actual sensitive credit card data. This allows for simplified one-click checkouts for online shopping carts, easier after-sale adjustments, as well as a safer way to implement recurring payments for monthly subscription services.
Processor-agnostic omnichannel tokens are flexible in that they operate across multiple avenues; a customer can pay with a card online and then make a return or adjustment in-store without having to re-present their card. This functionality operates in both directions and is conducive for BOPIS (Buy Online Pickup In Store), Curbside, and shifting to recurring payments.
If you’re operating with an already established collection of tokens, we’ve outlined the steps below to migrate them into (or out of) the Datacap platform. This is a general overview; technical details can be provided upon request.
Migrating Tokens within the Datacap Environment – Changing Processors or POS Providers
- Changing Processors – No Updates Required!
Note: If utilizing COF (Card on File) for Recurring Transactions, the POS will need to remove existing “RecurringData” field to re-enroll with the new processor. - Changing POS Providers or Billing Partners
Token Groups are specific to the Datacap billing partner. If the updated Deployments are being managed by a new billing partner, a request will need to be submitted to Datacap Support (support@dcap.com) including both the New and the Original Deployment ID’s. We will then map the token group to the new partner.
Importing Tokens to Datacap from Third-Party Provider
For partners with an existing collection of tokens from a third-party processor or gateway, Datacap can coordinate with the original payment provider to convert those values into Datacap tokens. Here’s what you can expect from the process. Additional details and a full technical brief can be provided upon request.
- Establish a Datacap account.
- The tokens will need to be directed to a particular merchant account, so creating a Datacap MID will need to occur first.
- Encrypted Transfer
- It’s likely the original provider will require a Liability Waiver.
- Once their legal policies are satisfied, the original payment provider will send Datacap a .CSV file with the token PAN data via Secure Transfer; i.e. SFTP or PGP encryption
- New Token Delivery
- Datacap will then provide new token data to merchant/partner
- The POS partner will need to complete the mapping of tokens to customer profiles
Exporting Tokens from Datacap to Third-Party Provider
Note: Charges apply. Be sure to coordinate with POS Provider or Datacap billing partner for associated costs.
Datacap is sorry to see you go, but we will assist and cooperate with your new payments provider to convert Datacap tokens into their environment. Here’s what you can expect from the process. Additional details and a full technical brief can be provided upon request.
- Info Gathering and Responsibilities
- The merchant account and POS partner need to be identified along with the new hosting entity. Datacap will need contact information for the purposes of a liability waiver. This will be sent to both the End-User (Requestor) and the new processor/gateway (Third Party).
- Token identification
- POS Partner/Merchant will provide a list of Datacap tokens for scoping and to quote the cost of the migration.
- Encrypted Transfer
- With Liability Waiver and Project Invoice completed, Datacap and the new provider will coordinate to create a secure transfer environment via SFTP or Partner Public Key.
- Using one of the above secure methods, Datacap will provide a .CSV file with the token PAN data to the merchant/partner.
- The new payment provider will then map that information to their own token environment.
