Advanced Integrations use SecureForm to capture secure data and tokenize client side. This is typically done prior to a server to server transaction. The response is a single use token. Transactions are then conducted later useing the kernel API and single use token.
Include value.js on the page and setup configurations.
window.valueio_write_only_token = "497aa694-297b-4204-8f51-b86dd0ec5a38";
window.valueio_form_selector = "#your-checkout-form";
window.valueio_secure_form_title_1 = 'Your Store Name Here';
window.valueio_secure_form_title_2 = 'Your Store Callout Here';
Include the value.css link between <head> and </head>.
Many more configurations below for bending the work flow to your needs.
Card Present - USB Swiper
From a developer perspective, setting up USB swipers is as easy as telling the value.io support team your account requires them. Once we eneable USB swipers, forms will be built out with them in mind. The below button was built out using the code from our Simple Integration Tab above. The only difference is, we have USB Swipers enabled for the linked demo sub-account.
Card Present - EMV Terminal
The Value.IO team has worked hand in hand with Dejavoo℠ to build a fully cloud ready EMV terminal solution. Below outlines the flow of transaction data. In our system, we consider terminals "Destinations." This means that like our USB Swiper example, the bulk of code changes takes place on the Value.IO side, and we abstract out the communications to the devices for you. Read below for more information, and contact us with questions.
1) POS System Launches SecureForm.
a) POS System initializes a transaction via "simple integration" such as example above.
b) SecureForm knowing the destination automatically prompts 2a below.
2) Terminal Transaction
a) Value.IO initializes transaction via terminal. POS system does not require any development beyond the simple integration to make this happen.
b) Terminal runs transaction directly to processor and returns response as well as signature capture image when applicable.
3) Vertual Termianl
If 2a fails, and terminal is seen as unavailable on the local network for any reason, USB Swiper or key entry can be used as backup via 3. Refunds and credits can also be issued w/o requiring terminal connectivity from the back office utilizing 3.
SecureForm℠ API Configuration Documentation
(Required) a value.io token associated with your value.io account with the write_only role
(Optional) the name of the field in which the secure token will be sent
(Optional) default is secure_form, alternate option is secure_field
(Optional) the id of a previously created untransacted payment record
(Optional) a credit card record single use token to be used for a payment
(Optional) the id of the destination to be used for a payment
(Optional) default is payments, alternate option is credit_cards
(Optional) order amount
(Optional) order number
(Optional) in addition to posting the merchant's form with the secure field, can also redirect to a url instead
(Optional) user defined callback method to be called on value secure form or secure field success
(Optional) user defined callback method to be called on value secure form or secure field failure
(Optional) user defined callback method to be called on value secure form cancel
SecureForm℠ Specific Configurations
(Optional) the title for the iframe form
(Optional) the callout for the iframe form
(Optional) configures the iframe form to include name fields. Accepted values are 'true' and 'false' (default)
(Optional) configures the iframe form to include address fields. Accepted values are 'true' and 'false' (default)
(Optional) configures the iframe form to include the zip address field when valueio_secure_form_collect_address is 'false'. Accepted values are 'true' and 'false' (default)
(Optional) configures the iframe form to include order fields. Accepted values are 'true' and 'false' (default)
(Optional) configures the iframe form to include an order comment. Accepted values are 'true' and 'false' (default)
(Optional) configures the iframe form to include credit card fields. Accepted values are 'true' (default) and 'false'
(Optional) This dertimines whether created credit card records are stored in the credit card vault or not. Accepted values are 'false' (default), 'true', or 'collect'. Setting to 'collect' will display a 'save card' checkbox on the form.
(Optional) This dertimines whether a payment record is automatically transacted against a back end processor, against a terminal, or not transacted. Accepted values are 'true' (default), 'false', and 'terminal'.
(Optional) This dertimines whether a transaction is only authorized or authorized and captured. Accepted values are 'true' and 'false' (default)
(Optional) This dertimines whether the form automatically submits with configured data on page load. Accepted values are 'true' or 'false'(default).
(Optional) This dertimines the nav bar color.
(Optional) This dertimines the nav bar text color.
(Optional) This dertimines the form text color.
(Optional) This dertimines the form input text color.
(Optional) This dertimines the form background color.
(Optional) This dertimines the form input background color.
(Optional) This dertimines the fieldset border color.
(Optional) This dertimines the form submit button color.
(Optional) This dertimines the form submit button text color.