Platform Docs

Custom Tenders

Overview

Custom tenders allow developers to build out additional payment options that can launch as either customer-facing or merchant-facing experiences. These user flows enable additional payment methods for a given merchant, such as QR scanning.

This tutorial walks through the process of building an app that can create a custom tender type. It also implements a payment flow that can be initiated from the Register, Sale, and Secure Payment apps.

Use Cases

Clover Mini or Clover Mobile:

  • Initiated through the Register or Sale apps for a merchant-facing experience
  • Initiated through the Secure Payments app for a customer-facing experience

Clover Station or Clover Mini with a tethered Clover Mini:

  • Initiated through the Secure Payments app on a tethered Clover Mini for a customer-facing experience
  • Initiated through the Register or Sale apps for a merchant-facing experience

Semi-integrated approach of a third-party POS with a tethered Clover Mini:

  • Initiated through the Secure Payments app on a tethered Clover Mini for a customer-facing experience

Design Requirements

  1. There must be a Cancel button so the customer or merchant can exit the payment flow.
  2. The graphic for the tender button must be a logo with one of the following resolutions:
Type
Resolution

MDPI

230 x 104px

HDPI

345 x 156px

  1. You must include a logo asset corresponding to each experience (customer and/or merchant).
    This should be:
    • A white (#FFFFFF) logo with a transparent background for the Secure Payments app (for a customer-facing experience).
    • A gray (#666666) logo with a transparent background for the Sale app (for a merchant-facing experience).

If you do not provide a logo, the button will display the name of the custom tender.

NOTE

You may want to review the Example App in the Android Examples repository to see how we've implemented these features