API
Log In Support
  • Clear

    • Get Started

      • Overview

      • Platform Sign Up

      • API Basics

    • Integration

      • Setup Platform

      • Onboard Merchants

      • Enable Merchants

      • Process Payments

      • Payout Merchants

      • Manage Payment Operations

      • Test and Launch

  • Link

    • Get Started

      • Overview

      • Platform Sign Up

      • API Basics

    • Integration

      • Setup Platform

      • Onboard Merchants

      • Process Payments

      • Manage Payment Operations

      • Test and Launch

    • CARD PRESENT SOLUTIONS

      • Get Started

        • Overview

      • Terminals

        • Acquire Terminals

        • Onboard Terminals

        • Authorize Cards

        • Process Payments

        • Test and Launch

      • Mobile Card Readers

        • Build Mobile App Prerequisites

        • Acquire Mobile Card Readers

        • Pair A Device

        • Authorize Cards

        • Process Payments

        • Test and Launch

      • Card Present Resources

        • Provide Receipts

    • API Reference

    • Resources

      • Payment Life Cycles

      • Server to Server Integration

      • Platform Legal Certification

      • Security Certification

      • Risk Certification

      • CIP and KYC Certification

      • Card Network Rules

      • Disputes Deep Dive

    • Cookbooks

      • Build Payment Support Tools

      • Reporting

      • Implement Merchant IC+ Pricing Model

      • Recurring Billing

      • Level 2 & Level 3 Processing

      • Style Credit Card iFrames

      • Support Merchants Outside the United States

      • Connect Merchants With SSO

      • Design A Retry Strategy

    • Release Notes

Home / Card Present / Terminals / Aquire Terminals

 

Acquire Terminals

 

In This Section
  • VeriFone P400
  • VeriFone V400m
  • Customize Terminals
  • Ensure Merchant Readiness
  • Fulfill Merchant Orders
  • Supporting Hardware

Once you’ve set up the Card Present SDK, you’re ready to begin integrating Terminals and their associated API extensions into your user flow.

The Terminals API resource represents the physical terminal hardware and allows your merchants to securely process in-person payments via credit or debit.

To get started with testing and development, you’ll need a stage environment terminal, test cards, and an iOS device. A stage environment terminal and the test cards will be provisioned by WePay.

As a note, this guide refers to Card Present SDK functions generically. You can find the function itself in the Card Present SDK package.

Contact WePay to request terminal quantity and environment (i.e. STG, PRD). WePay currently supports VeriFone V400m and P400 models as our pre-certified terminals. Once you physically receive terminals, collect the model and serial numbers for later use.


VeriFone P400

Note

This device is currently in BETA.

 

VeriFone P400

Features:

  • Contactless card reader (NFC)
  • Mag stripe card reader
  • Chip card reader
  • External power supply
  • WiFi and LAN connectivity

VeriFone V400m

Note

This device is currently in BETA.

 

VeriFone V400m

Features:

  • Contactless card reader (NFC)
  • Mag stripe card reader
  • Chip card reader
  • External power supply
  • Battery power supply
  • WiFi connectivity
  • Receipt printer

Customize Terminals

 

Design a terminal screen and provide it to your WePay team. Your platform’s terminals will be configured with your custom design prior to shipping out for merchants. Use the below design specs:

  • Dimensions: 320×480 px
  • Color Space: RGB
  • Alpha Channel: No

Idle Screen Template

  • PNG-Type: 24bit/Channels

Screen

Splash Screen Template

  • PNG-Type: 8bit/Channels

Splash


Ensure Merchant Readiness

 

Note

The Terminal Capability is an experimental feature currently in development. Requirements for enablement are documented below.

A minimum set of onboarding data must be provided to WePay before a merchant’s Terminals Capability will be enabled. To check a merchant’s enablement status, make a GET /accounts/{id}/capabilities API request and examine the boolean value for the terminals.enabled parameter.

Link Integrations

Partners leveraging WePay’s Link solution for merchant onboarding should remind merchants to visit their merchant dashboard and provide complete verification information along with bank account information for payouts. WePay will not allow merchants to order terminals before their onboarding information has been provided.

Clear Integrations

Partners leveraging WePay’s Clear solution for merchant onboarding must ensure that the merchant’s Terminal Capability is enabled. To determine the status of a merchant’s Terminal Capability, send a GET /accounts/{id}/capabilities request and examine the terminals.enabled parameter in the response.

Legal Entities Required Parameters & Objects

  • country
  • legal_form
  • phone
  • address
  • controller.name
  • controller.email
  • controller.phone
  • controller.date_of_birth
  • controller.social_security_number
  • terms_of_service

Accounts Required Parameters & Objects

  • name
  • description
  • industry.merchant_category_code

If your merchants will process Card Present and web transactions, all the above requirements except address will be met by enabling the Payments Capability.

If a merchant is not enabled for Terminals, the current_issues structure will outline why. Reasons will typically include incomplete onboarding or missing requirements from above..

For further details and Clear onboarding requirements, see Fulfill Capabilities and Verifications.

 

Due to the above prerequisite, it is recommended to block merchants from ordering terminals from you until they have fulfilled these requirements. If a POST /terminals request is sent before the merchant has provided the necessary information, the API will respond with an ACCOUNT CANNOT CREATE TERMINALS error.


Fulfill Merchant Orders

 

Once you physically have terminals, you can begin testing and development, and designing your user flow.

Link Integrations

Partners integrating WePay’s Link solution will not need to implement fulfillment. Merchants will order terminals directly through their Chase dashboard.

Clear Integrations

Partners integrating WePay’s Clear solution must design and implement the fulfillment user flow. This flow solves for merchants ordering and receiving their terminals. Only provide access to this flow once the merchant has met the above minimum requirements for using terminals.

You have a few options with regards to fulfilling merchant Terminal orders:

End User Referral

POS Portal will setup a custom-branded microsite where you direct merchants to place orders. POS Portal will then fulfill orders.

End User Referral Fulfillment

Contract Deployment

Merchants order terminals from you, the platform, and you in turn submit the order to POS Portal. POS Portal then manages fulfillment and logistics on your behalf.

POS Portal Fulfillment

Wholesale

You, the partner, completely manages fulfillment by obtaining terminals wholesale from POS Portal, and managing shipment and stock logistics for your merchants.

Wholesale Fulfillment

Regardless of the fulfillment process your platform implements, it’s important to record the merchant’s WePay Account ID along with the terminal’s model and serial numbers. These will be used for terminal onboarding.

Note

If a merchant receives a terminal which has not been onboarded and turns it on, they will receive an error on the Terminal stating “Downloading error; missing merchant data.”

Your platform can either:

  • Standardize terminal options and disclose how the Terminal will work to merchants prior to ordering, OR
  • Allow merchants to customize terminal options in your UI

The latter option should provide guidance for merchants regarding the customizable options. Read more about terminal configurations here. Additionally, if the configuration is ever updated, the terminal itself will also need to be updated before those changes are applied.


Supporting Hardware

 

All technical & device support is managed by POS Portal. That said, your platform can and should provide these hardware guides to your merchants:

  • download the quick start guide
  • download the V400m setup guide
  • download the P400 setup guide

Link Integrations

You, the platform, are expected to provide support for all point of sale related questions.

WePay/Chase will provide end-user support for all terminal and payment related questions via:

  • Email
  • Chat

Clear Integrations

You, the platform, are expected to provide end-user (Tier 1) support for merchants. This includes all point of sale questions in addition to terminal and payment related questions.

WePay/Chase will provide support to your platform (Tier 2) for terminal and payment related questions.

 


Next Up: Onboard Terminals

Integrate terminals into your platform offerings.

  • Configure terminals
  • Onboard terminals
  • Use and manage terminals

 

Onboard Terminals

 


Questions? Need help? Visit our support page!

Company

  • About
  • Careers
  • Blog
  • News & Events

Resources

  • Knowledge Center
  • Terms of Service
  • Privacy Policy
  • Security
  • Support

Developers

  • Documentation
  • Engineering Blog

Customers

  • Case Studies

Product

  • Link
  • Clear
  • Core
  • Contact Sales
© 2020 WePay Inc.