Get Started

Product Guide

This guide provides an overview and shows differences among Groovv Integrated Payments APIs. It is intended for integrators who want to incorporate payments into a custom desktop or web (cloud) application.

Groovv Integrated Payments offers both hardware-based (payment devices) and software-only (eCommerce) solutions or a hybrid of these modes. This guide will help you determine the solution that would be best for your software application. It will also provide the available tools for integrating payments into your application as well as workflow models for your payment use cases.

Get Started

Getting Started Guide

This document outlines the preparatory steps that should be completed before you start working with our toolkits.

Below are the two toolkits that will be referenced in this document. While it is possible that your solution could use only one or the other API, it is most likely that you will need a combination of both.

  • Groovv Integrated Payments REST API: This allows you to accept basic payments
  • Groovv Integrated Payments SOAP API: This provides for extended payment workflows
Get Started

Integration Guide

This guide is for developers who want to better understand how to use the Groovv Integrated Payments REST (In-Store) & SOAP (Online) APIs within a custom software application.

Technical capabilities and considerations are defined for integrating your application with the API calls for Groovv Integrated Payments. An overview provides help on choosing an appropriate code integration model, workflow and deployment model.

Get Started

Reference Guide

This document provides detailed, real-world payment processing use cases. It shows how the Groovv Integrated API toolkits can be used to create custom solutions and provides code samples for calling the APIs in C# and JAVA.

Groovv Integrated Payments provides several interfaces that can be used independently or combined to provide the full set of features required in your custom application. The two toolkits that will be referenced in this document are “REST API” (In-Store API) and “SOAP API” (Online Payments API).

Get Started


This document provides details of all REST (In-Store) API methods and detailed code samples. The REST API requires the use of a payment device.

Topics covered include the registration process for payment devices, obtaining and entering pairing code between the point of sale software and payment devices, authorization headers, security considerations and more.

Get Started


This document provides details of all SOAP (Online) API methods and detailed code samples. Note that payment devices are not required.

The Groovv SOAP API provides a standardized web services interface and uses WSDL files to describe the methods and objects that are made available by a web service. The SOAP interface can be used with any programming language that is able to communicate with an HTTPS connection, and several guides are provided that give specific setup instructions on using SOAP with common programming languages.

Get Started

Castles MP200 Hardware Guide

This document provides detailed guidance on integrating with the Castles MP200 payment device rather than a traditional payment terminal.

The MP200 is a handheld, wireless payment device that accepts all payment types including magstripe and EMV chip cards, as well as NFC payments like Apple Pay. The device provides greater mobility and flexibility than a wired terminal while integrating payments into your software.

Sign Up with Groovv

When you register with us, you’ll gain access to download our documentation and get started.