Paying with Stored Data (Token)

note

Remember that these API calls will be HTTP POST requests to the TCP/IP address where DeviceHub is installed. Typically, this address will be:

POST http://localhost:17000

You can use the option to perform operations with DeviceHub or take advantage of our online payment functions (e-commerce) to carry out operations with cards stored in Sipay (tokenization)

CallSpecificFunction 6 - Sale with a card stored in the vault

This functionality performs the sale transaction on a card previously stored in the vault given its contract number, also known as token identifier.

Parameters:

The header data must be the same as in all transactions.

• Function: 6
• Modifier: 1 or 2 or 4
• Parameter1: string type, sale Ticket number.
• Parameter2: string type, Contract number or token identifier for charging with the stored card.
• Parameter3: string type, Sale amount. (See Note1)

If you have DCC operation contracted and the stored card allows DCC, the card's currency can be automatically applied. See the table of values for the modifier.

Value Table for Modifier

MODIFIER	COMMENTS
1	Sale operation. If the card allows DCC, the default foreign currency will be applied.
2	Used in returns.
4	Sale operation. If the card allows DCC, the default local currency (euro) will be applied.

Note1: Amount in the same format as the transaction with 10 digits, where the last 2 are cents. Ex: €1.25 -> 0000000125

CallSpecificFunction 6 - Return with a card stored in the vault

This functionality performs the return transaction on a card previously stored in the vault given its contract number.

Parameters:

The header data must be the same as in all transactions.

• Function: 6
• Modifier: 2
• Parameter1: string type, sale Ticket number.
• Parameter2: string type, Contract number or token identifier of the stored card.
• Parameter3: string type, Amount to return. (See Note1)

Note1: Amount in the same format as the transaction with 10 digits, where the last 2 are cents. Ex: €1.25 -> 0000000125