The SensePass token migration process allows merchants to securely transfer customer payment information for tokenization.
This process involves the merchant sending a structured Excel file, which contains sensitive customer data such as credit card numbers, expiration dates, and other relevant information.
The process can be completed in two distinct workflows:
Workflow 1: Generating New Tokens
File Submission: The merchant submits an Excel file following the prescribed format available on our documentation page. This file should include all required customer data fields.
Tokenization by SensePass: Upon receiving the file, SensePass processes the data by generating new, unique tokens for each credit card entry. These tokens are securely mapped to the original payment information within the SensePass system.
File Return: SensePass returns the processed file to the merchant. This file will contain the newly generated tokens, replacing the original credit card numbers, ensuring that sensitive data is securely handled.
Workflow 2: Using Merchant-Specified Tokens
File Submission: The merchant submits an Excel file in the standard format, including the existing tokens that they wish to retain. The file should also include the corresponding credit card numbers and other required customer data fields.
Token Matching by SensePass: SensePass processes the file by matching the provided tokens to the corresponding payment information within the system. This allows for the creation of identical tokens within the SensePass environment, ensuring seamless continuity for the merchant.
File Return: After processing, SensePass returns the file to the merchant with the specified tokens mapped to the original data, ensuring that the migration is completed without altering the token structure.
SensePass follows stringent security protocols to ensure the safe handling of sensitive customer information throughout the token migration process.
All data is encrypted during transfer and processing, adhering to SOC 2 and PCI DSS standards.
API for retrieving input from consumer using SensePass Tags and EMV devices.
POST https://api.sensepass.com/api/transactions/customer-input
For terminal agent invoke use this endpoint: http://localhost:8003/api/transactions/customer-input
| Name | Type | Description |
|---|
See Transactions entity schema:
POST https://api.sensepass.com/api/transactions/customer-input/reset
For terminal agent invoke use this endpoint:
http://localhost:8003/api/transactions/customer-input/reset
| Name | Type | Description |
|---|
deviceId* | string | unique device ID provided by SensePass |
deviceId* | string | unique device ID provided by SensePass |
inputs* | array |
API for getting device ID using SensePass tags.
This API should be called once on new tag assignment for a register, then the register saves the device ID for the next transactions until un-pairing proccess occur.
POST https://api.sensepass.com/api/devices/match
API for getting device ID using SensePass tags.
| Name | Type | Description |
|---|---|---|
deviceAliasKey is the device ID created for the tag.
Array of
pinCode*
string
SensePass Tag ID - it's located below the QR code, for example: 53K-HMD-786
apiKey*
string
Location or Merchant API key
deviceId
string
Optional - Device ID of existing register, will add the tag to this device instead of creating a new device ID
posName
string
The name of the register, this value will be shown in merchant dashboard and partners dashboard