Developer Central

## Sections
• [iPOSpays Developer Central](https://app.theneo.io/dejavoo/developer-central/developer-central.md): SPIn (Semi-Integration) Easily integrate Dejavoo payment terminals with POS systems, restaurants, kiosks, and more (for Merchants). Freedom to Design.js Build custom checkout pages while maintaining PCI compliance via our simple API (for Merchants). Hosted Payment Page Use our pre-built, customizable checkout page for easy, compliant online payments (for Merchants). WooCommerce Ext. Seamlessly integrate iPOSpays with your WooCommerce store for redirect or embedded payments (for Merchants). Terminal Integrations Integrate with Dejavoo terminals via SDKs for hardware access and payments (DvPayLite) (for ISVs and Merchants). Migrate to iPOSpays Securely migrate merchant and customer data from other payment providers to iPOSpays (for Merchants). Live Data Feed Access real-time transaction data directly in your portal or CRM (for ISOs, ISVs, and Merchants). iPOS Transact API Perform key functions (sales, refunds, pre-auth) directly from your platform (for Merchants). Merchant Onboard Streamline merchant onboarding from your CRM or portal (for ISOs). Tap to Pay on Android Enable contactless payments within your Android app (for Merchants). Tap to Pay on iPhone Enable contactless payments within your iOS app (for Merchants). Recurring Payments Enable merchants to process recurring charges, voids, and refunds directly from their software (for ISVs).
• [SPIn Specification](https://app.theneo.io/dejavoo/developer-central/spin-specification.md): Secure Payment Interface SPIn is a robust semi-integration solution that bridges Point of Sale (POS) systems—such as cash registers, billing software, or tills—with Dejavoo Payment Terminals. By creating a secure, cloud-based connection, SPIn enables the Merchant’s Host System to communicate seamlessly with Dejavoo terminals. This integration allows the Host System to send payment requests to the terminal and receive transaction data back upon completion. The SPIn solution enhances operational efficiency by simplifying payment reconciliation and reducing the risk of human errors. Importantly, sensitive cardholder data (e.g., PAN, expiration dates) never touches the Host System, which eliminates PCI compliance for merchants. Use Cases Third-party POS providers aiming to offer merchants a payment solution free from PCI compliance concerns. Merchants seeking a seamless, unified point-of-sale experience that integrates payment acceptance with record-keeping systems. Integration Options REST API : For integration using RESTful methods, refer to the SPIn REST API Documentation . SOAP API : For XML-based requests and responses, continue exploring this document. SPIn is designed to streamline payments, minimize complexity, and provide merchants with a secure and hassle-free transaction process. All of our payment applications included in this page comply with PCI DSS (Payment Card Industry Data Security Standard). PCI DSS is a set of security standards designed to ensure that any company accepting, processing, storing, or transmitting credit card information maintains a secure environment. By adhering to these guidelines, we ensure that all payment data is handled with the highest level of security, protecting sensitive information and preventing data breaches.
• [Freedom To Design](https://app.theneo.io/dejavoo/developer-central/freedom-to-design.md): Freedom to Design is a JavaScript framework that allows merchants to collect sensitive payment information from their customers without exposing their websites to sensitive information. This can be done while allowing merchants to retain full control over the look and feel of their checkout experience. Use Cases Merchants who have their own eCommerce site and want the freedom to design their checkout page without the burden of compliance can use Freedom to Design. It is an easy-to-integrate API that allows merchants to accept payments safely and securely while retaining their brand theme and consistency throughout. Payment Methods Supported Credit/Debit Cards Google Pay Apple Pay ACH All of our payment applications included in this page comply with PCI DSS (Payment Card Industry Data Security Standard). PCI DSS is a set of security standards designed to ensure that any company accepting, processing, storing, or transmitting credit card information maintains a secure environment. By adhering to these guidelines, we ensure that all payment data is handled with the highest level of security, protecting sensitive information and preventing data breaches.
• [Hosted Payment Page](https://app.theneo.io/dejavoo/developer-central/hosted-payment-page.md): Hosted Payment Page (HPP) is a checkout page that can be integrated into an eCommerce website or any software that wants to accept payments without any compliance burden. Use Cases Add a checkout page to a website Show the checkout page as a new page or light-box overlay in the website, Send SMS or Email to customers with the link to collect payment Embed the URL into a QR code and print it on invoice, pre-sale ticket, cash register receipts. Payment Methods Supported Credit/Debit Cards ACH Google Pay Alternative Payments All of our payment applications included in this page comply with PCI DSS (Payment Card Industry Data Security Standard). PCI DSS is a set of security standards designed to ensure that any company accepting, processing, storing, or transmitting credit card information maintains a secure environment. By adhering to these guidelines, we ensure that all payment data is handled with the highest level of security, protecting sensitive information and preventing data breaches.
• [Recurring Payments](https://app.theneo.io/dejavoo/developer-central/recurring-payments.md): The Recurring Payments API empowers Independent Software Vendors (ISVs) and third-party platforms to seamlessly integrate automated billing and payment management into their own applications using the iPOSpays framework. By embedding this API, ISVs can enable merchants to process recurring charges, voids, and refunds directly from their software—eliminating the need to access the iPOSpays portal for routine payment operations. This API works alongside Hosted Payment Pages (HPP), SPIn (Semi-Integrated Payments), and Freedom to Design.js, which securely handle the initial card data capture and tokenization. Once a card token is generated through any of these solutions, it can be used by the Recurring Payments API to execute future payments automatically—making subscription, membership, and installment-based billing effortless. Whether integrated into a membership platform, billing system, or self-service solution like a kiosk or vending application, the Recurring Payments API allows ISVs to deliver a unified, efficient, and secure payment experience that scales with their merchants’ needs. Use Case Membership and Subscription Billing ISVs developing applications for gyms, clubs, or any subscription-based services can leverage the Hosted Payment Page, SPIn, or Freedom to Design.js to capture the initial payment and securely tokenize the customer’s card. Once tokenized, the Recurring Payments API enables automated billing—whether monthly, quarterly, or annually—without requiring any additional action from the merchant or customer.
• [iPOSPays WooCommerce Extension](https://app.theneo.io/dejavoo/developer-central/ipospays-woocommerce-extension.md): Merchants who have an eCommerce site built with WooCommerce and want to accept payments on their site without compliance concerns can use the WooCommerce iPOSpays Payment Gateway plugin. It is an easy-to-integrate plugin that allows merchants to accept payments safely and securely while retaining their brand theme and consistency throughout. Payment Methods Supported Credit/Debit Cards Bank (ACH) Google Pay Apple Pay Supported Fee Programs Custom Fee and Surcharge ACH with Dual Pricing and Apple Pay integration Demo Checkout Page For ISOs who wish to demo the product, please use our self-created demo WooCommerce store to experience the product firsthand. Demo Checkout Page Add description here All of our payment applications included in this page comply with PCI DSS (Payment Card Industry Data Security Standard). PCI DSS is a set of security standards designed to ensure that any company accepting, processing, storing, or transmitting credit card information maintains a secure environment. By adhering to these guidelines, we ensure that all payment data is handled with the highest level of security, protecting sensitive information and preventing data breaches.
• [Payment Terminal Integrations](https://app.theneo.io/dejavoo/developer-central/payment-terminal-integrations.md): Developer Integration Kits for Dejavoo Payment Terminals DVStore DVStore is a powerful marketplace application designed to centralize and streamline payment solutions for merchants. Independent Software Vendors (ISVs) can list their applications on DVStore, giving merchants access to a diverse ecosystem of apps directly on their Dejavoo payment terminal. This eliminates the need for merchants to invest in multiple hardware devices, ensuring both convenience and cost efficiency. List Now For more information about how DVStore works and how to manage applications, refer to the documentation below. DvStore Deep Linking Integration Third-party applications listed on DVStore can integrate seamlessly with the Dejavoo payment application, DvPayLite, for payment processing, providing a unified and efficient payment experience for merchants. We offer two modes of Deeplinking integration: Deep Linking in Intent Mode What it is : This mode is tailored for Android applications, using Android Intents to navigate to specific screens or perform actions. How it works: An Intent is sent to the app, specifying the desired activity or action. The app processes the Intent and included parameters to determine its behavior. Through Intent Mode Deep Linking in URI Mode What it is : A cross-platform mode leveraging Uniform Resource Identifiers (URIs) that works seamlessly on Android, iOS, and web environments. How it works : A URI acts as a direct link to content or functionality within the app. The URI is mapped to the app’s routing system during development to determine navigation or actions. Through URI Mode How to Change Your Payment Terminal to UAT Mode To perform testing or use UAT mode for integration, the payment terminal needs to be switched from Production to UAT (User Acceptance Testing) mode. Check out the document below to know how to verify the current environment (Production) and change the payment terminal to UAT mode using DVStore. Click Here Peripheral/Hardware SDKs Third-party applications listed on DvStore can also utilize Dejavoo terminal peripherals to extend their functionality. Seamlessly integrate with our SDKs to access powerful hardware features: Printer SDK Swipe Reader SDK All of our payment applications included in this page comply with PCI DSS (Payment Card Industry Data Security Standard). PCI DSS is a set of security standards designed to ensure that any company accepting, processing, storing, or transmitting credit card information maintains a secure environment. By adhering to these guidelines, we ensure that all payment data is handled with the highest level of security, protecting sensitive information and preventing data breaches.
  • [Peripheral SDKs](https://app.theneo.io/dejavoo/developer-central/payment-terminal-integrations/peripheral-sdks.md): If you wish to modify features on your Dejavoo terminal at the hardware level, follow the instructions provided in the SDKs given below. Printer SDK Scanner Reader SDK Swipe Reader SDK
• [Tap to Pay on Android](https://app.theneo.io/dejavoo/developer-central/tap-to-pay-on-android.md): Tap to Pay on Android is a technology that turns smartphones into payment devices, using NFC to process transactions in EMV mode. Governed by the PCI-CPOC standard, this solution includes certified libraries, user interfaces, and branding for quick market deployment. The SDK gives mobile app developers full control until payment initiation, after which it completes the transaction and reports back via callback functions. Use Cases Third-party mobile applications listed on app stores can integrate Tap to Pay, allowing their merchants to accept payments directly through their devices. Merchants with NFC-enabled devices can process contactless payments without the need for additional hardware. Mobile app developers can integrate the Tap to Pay SDK for rapid and secure payment processing. API Access The Tap to Pay API provides easy programmatic access for contactless transactions, using standard REST, JSON, and Basic Authentication protocols. This ensures simple, secure, and efficient integration for developers. All of our payment applications included in this page comply with PCI DSS (Payment Card Industry Data Security Standard). PCI DSS is a set of security standards designed to ensure that any company accepting, processing, storing, or transmitting credit card information maintains a secure environment. By adhering to these guidelines, we ensure that all payment data is handled with the highest level of security, protecting sensitive information and preventing data breaches.
• [iPOS Transact](https://app.theneo.io/dejavoo/developer-central/ipos-transact.md): The iPOS Transact API empowers merchants to streamline their payment processes by enabling void, full or partial refunds, and sale transactions using card tokens directly from their own CRM or billing software. With this API, merchants can bypass the need to log in to the iPOSpays portal for many transaction types, improving efficiency and integration with third-party applications. However, the API is not a replacement for a Hosted Payment Page (HPP) or Freedom to Design (FTD) solutions. While void and refund transactions can be executed directly, sale transactions require a card token. These tokens can only be generated through Hosted Payment Pages or SPIn (Semi-integrated Payments). For example, a merchant running a gym membership program can use the Hosted Payment Page to collect the first payment via a payment link. Upon successful payment, the card token is returned as part of the response. The merchant can store this token in their system and later use the iPOS Transact API to charge the customer for recurring payments without further intervention. It is also worth noting that the Hosted Payment Page and WooCommerce plugin utilize the iPOS Transact API as their underlying payment mechanism. Use Cases Here are some scenarios where the iPOS Transact API can provide significant value to merchants: Void or Refund Transactions in Semi-Integrated Payments Merchants using semi-integrated setups (e.g., cash registers paired with POS terminals) can perform void or refund transactions directly from their system without requiring the card used in the original transaction. Integration for Membership-Based Services Merchants managing membership-based services (e.g., gyms) can integrate the Hosted Payment Page to collect the initial payment and save the card token. The iPOS Transact API can then be used for future charges, voids, or refunds without requiring manual intervention. Simplified Payment Operations The API enables merchants to streamline operations by integrating payment functionality directly into their existing software solutions, reducing the need for multiple tools or platforms.
• [Clear Card Encryption](https://app.theneo.io/dejavoo/developer-central/clear-card-encryption.md): The Clear Card Encryption API enables secure card encryption for PCI DSS-compliant third-party applications that handle clear card data. This API is designed for integrators who collect sensitive cardholder data within their own user interface and need a secure way to encrypt the card. Once encrypted using the public key, the resulting encryptedCardData can be used to perform transactions using iPOS Transact API. This API is only available to certified platforms that meet PCI DSS requirements for handling clear card data. iPOSpays is not responsible for uncertified applications using this API. Key Benefits Complete Control Capture card details within your own UI and pass the encrypted data to iPOSpays for processing—ideal for platforms that are PCI DSS-compliant. Secure Encryption Transforms clear card data into encrypted card data using PCI-compliant endpoints. Seamless Integration Works alongside the standard iPOS Transact API, so once the encrypted card data is received, transactions can proceed without merchant login or hosted pages. Built for Certified Systems Designed exclusively for systems already meeting PCI DSS requirements. How It Works Authenticate Generate an access token using your API and secret key (Which will be provided to you via email through your Dejavoo representative). This token authorizes your system to interact with the iPOSpays APIs. Encrypt Card Data Use the public key to encrypt the raw card data (PAN, expiry, CVV) Use Encrypted Card Data in iPOS Transact Send the encrypted card data with the standard iPOS Transact API to initiate sale, refund, or void transactions.
• [FEED Integration](https://app.theneo.io/dejavoo/developer-central/feed-integration.md): Use Cases For Independent Sales Organizations (ISOs) If you have your own Customer Relationship Management (CRM) system, you can develop custom dashboards and reports for real-time monitoring and analysis of transactions. FEED gives you more flexibility to manage transactions and settlements for your merchants. For Independent Software Vendors (ISVs) Integrate FEED into your software solutions to provide your clients with advanced features for tracking and reporting payments. Offer real-time data validation and reporting, making your software more valuable. Tailor FEED integration to each client’s specific needs, creating unique solutions that improve their experience. For Merchants (Multi-Store) If you have your own CRM, you can integrate FEED to view and manage all transactions from all your stores in your own CRM. Manage your transactions and settlements with more flexibility to fit your business needs Authentication Process We have provided three types of authentication in FEED services: Default - Deprecated Basic Authentication HMAC Default: Deprecated If the integrator is enabled by default, we will send the payload without any authentication. We will only require the event trigger URL as mandatory. Basic Authentication If the integrator is enabled with Basic Authentication, they need to provide the username (APIKey) and password (SecretKey) in the portal along with the Event Trigger URL. We will send the payload and authorization in base64 format. Title Description Header Data Authentication Basic (Base64 String) HMAC If the integrator is enabled with HMAC then we will provide the two options whether he can provide his own HMAC key and share with iPOSPays team or we will provide the Key generate button it will be used to generate the HMAC key that needs to be copied by the integrator. Logic used for the HMAC Generation: String param_data = param_value1|param_value2|param_value3|………|; String final_data = secret_key|param_data; String secureHash = generate_secure_hash_using_SHA512_and_secret_key; All of our payment applications included in this page comply with PCI DSS (Payment Card Industry Data Security Standard). PCI DSS is a set of security standards designed to ensure that any company accepting, processing, storing, or transmitting credit card information maintains a secure environment. By adhering to these guidelines, we ensure that all payment data is handled with the highest level of security, protecting sensitive information and preventing data breaches.
• [OnBoard API](https://app.theneo.io/dejavoo/developer-central/onboard-api.md): Merchant Onboarding API enable ISOs to programmatically onboard and manage merchants, stores, and TPNs directly from external systems (CRM/portal), eliminating manual portal interaction. With this API, all data entered in your CRM or portal is automatically synced with the iPOSpays portal, enabling you to onboard merchants conveniently and efficiently. Supported Operations Title Description Title Entity Operations Merchant Onboard, Edit Store Add, Edit TPN Add, Edit, Get Details Key Capabilities Onboard a completely new merchant along with their first store and TPN. Enable merchant-level add-on features (e.g., Whitelisting) Expand an existing merchant’s setup by adding a new store and TPN. Request and retrieve required TPN parameter information like OTP, AUTH-TOKEN, SPIN details (i.e., Registered Id, AUTH-KEY) Enable or disable specific TPN parameters like SPIn Enable store-level add-on features (e.g., ACH) Prerequisites Before invoking any API in this document, the following conditions must be satisfied: The ISO (Independent Sales Organization) must already be onboarded in the iPOSpays portal. The following entities must be created and active, except the onboard API call: Merchant Store TPN (Terminal Profile Number) The integrator must possess: API Key Secret Key These are required to generate an Access Token , which must be included in all subsequent API calls. Contact support@dejavoo.io and CC your sales executive to get the API and Secret Key
• [Batch Report](https://app.theneo.io/dejavoo/developer-central/batch-report.md): The Batch Report API allows integrated systems, such as CRMs, payment platforms, or merchant dashboards, to retrieve detailed reports for one or more closed batches. It provides complete visibility into batch activity, including: Processor configuration used (profiles) Itemized transactions Tips, fees, and tax calculations Cash and alternative payment summaries The Batch Report API supports batch data retrieval for transactions initiated across all iPOSpays-enabled payment environments, including physical POS terminals, virtual terminals, eCommerce payment interfaces, and APIs. Use Case: Merchants and partners can use this API to view: Batch-level settlement details Summary and itemized transaction data Fee, tax, and tip breakdowns Processor and terminal info What is a Closed Batch Report? A Closed Batch Report contains all transaction and financial details for a batch that has been submitted and settled. Once a batch is closed, its contents cannot be modified—making this report ideal for reconciliation, accounting, and compliance reporting. Who Should Use This API? This API is intended for: ISVs and SaaS platforms building merchant dashboards or portals Developers integrating with iPOSpays terminals and payment flows Merchants or partners seeking post-settlement financial data for audit, reconciliation, or reporting
• [Transaction Status Check](https://app.theneo.io/dejavoo/developer-central/transaction-status-check.md): The Transaction Status Check API allows merchants to query the current status of any transaction initiated through any iPOSpays-enabled payment environments, including physical POS terminals, virtual terminals, eCommerce interfaces, and APIs. This API supports both standard card payments and alternative payment methods, such as ACH and digital wallets. This is useful for confirming whether a transaction was: Successful Failed Pending Cancelled Or in any other custom-defined state.