1 of 93

NUMBER - Development Portal

Home

Embedded Payments Starts Here

Embedded payments are at the heart of everything we do, enabling ISVs and SaaS providers to integrate tailored payment solutions directly and elegantly into their platforms.

We understand the critical nature of payment processing and are committed to maintaining seamless operations. Our dedicated support team is available around the clock to provide immediate assistance and resolve any issues, ensuring your business can operate without disruption.

Get Your Business Started

Find out how long it takes to get started with Number

At Number, we know that running a business means juggling countless tasks. That's why we've made our payment integration as simple and efficient as possible, so you can focus on what really matters—growing your business.

Implementation timeline

Before you start using our services, you might want to gain more insight into the work required to integrate. We've prepared a rough implementation timeline to help guide you in your decision-making.

You can find a detailed integration guide by visiting the section.

To get your business started with Number, follow these general steps for implementation:

Phase

Duration

Task

Documentation

Developer Quickstart

Partnership isn’t just a word—it’s how we power payments.

Integrating payment services into your system is a complex task, and it grows all the more complex the more ideas and customization needs you have. We want to make that process as easy to follow as possible—from one developer to another.

See our Vocabulary to help you get started if you are new to payment services.

We've prepared this quickstart section to help you get started. We recommend going through all of the sections in order and then moving onto the Getting Started section to find out which integration option makes the most sense for you and how to implement it in your system.

Now, if you are ready to explore...

Authentication

A quickstart guide to authenticating with Number services

Basics

To authenticate to our services, depending on your integration of choice, you might need the following:

Querying and Filtering

Find the information you need through the API or Virtual Terminal

If you need to find a specific record in our database (such as a transaction or saved consent) or you need to find all records matching your criteria, you can either query our APIs programatically or use the Virtual Terminal to view and filter the records from its user interface.

REST API

To query records, you'll need to find a relevant method in the REST API reference.

When querying, you'll need to prepare the Query string. It should consist of variables that correspond to fields on the records and logical terms built using those variables.

All Query string variable options are fully described in the API reference under specific API methods and in the reference. You can use the variables to build logical terms, and you can build and join logical terms using "&&" for a logical AND or "||" for a logical OR.

Read about Number's query language in our reference.

Depending on the type of record you're querying (transaction, consent, ...), the variables you can use inside of a Query string will differ. The formatting rules do not change.

Example

As an example, if want to find settled ACH transactions made in January 2025 made using Verifone card readers, you can call or depending on which API you are using.

You can check the description of the Query string parameter or check the reference for section to find out that variable 'B' corresponds to transaction status, variable 'C' corresponds to date created, and 'U' corresponds to the transaction origin.

Each variable which requires an enum includes a description of valid values. Settled transactions have a transaction status of '2', and Verifone transactions have an origin of 'SDK'. To format the date correctly, follow the examples given for the variable.

You can combine the filters to build your Query string like so:

Virtual Terminal

You can filter consents, transactions, and other records through the Virtual Terminal user interface.

To log into the Virtual Terminal, you need to have a user account created through the Client Admin Portal as described in the quickstart guide.

Once you're logged in, see the navigation on the left and click on Scheduled to view scheduled payments, click on Settlement to view settlements, or expand Reports to find other reports. There, you'll be able to search and filter records using the user interface.

You can read more about using the Virtual Terminal in the guide.

Getting Started

Before you get started

To get the most out of using Number services, you'll need to define the type of integration (or integrations) you need, and learn some basic concepts around how to integrate.

In the next sections, you can read about all of the and find our to give you an overview of all the steps required to start using our services.

For all major types of integrations, there are additional integration guides or user guides under their respective sections.

Here are the articles in this section:

Basics

How to correctly integrate with Number and our backend

If you choose to use the REST API, we recommend you to read about Authentication, API Best Practices, and API Input Validation. You may also want to refer to the resources about Querying and Error Codes once you start working on the integration.

Here are the articles in this section:

API Input Validation

Basic details about input validation in the APIs

The following string values are validated within the APIs and will only allow a finite set of characters. If you send characters which are not allowed, you can receive an ErrCode of 7123.

Field / fields

Allowed characters

Firstname, Lastname

Alphanumeric, single quote, minus sign, period, space, ampersand, comma, question mark, forward slash.

Company, Title

Alphanumeric, minus sign, period, pound sign, underscore, comma, ampersand, forward slash.

Address

Testing Considerations

Responses

When Processing using the API or the VeriFone Middleware you should be ready to consume the following types of responses:

Approvals

Testing

Test your integration before going live.

Before you go live, you'll need to test your integration, and the Number team will need to validate it.

To help you with that, we've compiled all the information regarding transaction and consent verification, sandbox cards and test data, penny codes, and return codes into this section.

Here are the articles in this section:

Resources

Here are the articles in this section:

Tools and Downloads

Compilation of all tools and downloads from the documentation

API

All links and downloads for the REST API.

REST API downloads

Software Requirements

Minimum software requirements for running Number services

Number software is a collection of lightweight software products that can be customized to run on most platforms with minimal resource requirements. Although Number has a solution for most platforms, we do recommend the following requirements to run our products efficiently.

Processor minimum: Intel i5 Gen 5 and AMD Ryzen 5 RAM minimum: 8GB (4GB free)

Operating systems

Microsoft Windows 8.1+
MacOS Sierra 10.12+

Browsers

Microsoft Edge v122.00+
Google Chrome v122.0.626.1.111+
Mozilla Firefox v123.01+
Safari version v17.3.1+

API Reference

REST API

The API reference for the REST API

Our REST API can be used to integrate any frontend or backend application with Number and use all of our payment services. This way, you have full control over the presentation, and we'll handle the complex payment processes. We recommend following our REST API integration guide to get started. It'll teach you all of the generic concepts you need to correctly authenticate, consume API responses, and how to recognize and handle errors, alongside code examples.

Authentication

Authenticate user and retrieve session key

post: https://easypay5.com/APIcardProcREST/v1.0.0/Authenticate

{
  "AcctCode": "EP911XXXX",
  "Token": "2148B239CF6846BDA5D141BF4A4CFBE8"
}

{
  "AuthenticateResult": {
    "AuthSuccess": true,
    "ErrCode": 0,
    "ErrMsg": "",
    "FunctionOk": true,
    "MerchantList": [
      {
        "Address": "45 spring street portland Maine 04101",
        "Descrip": "Test Merchant 1",
        "ID": 1,
        "Location": "Test Merchant 1",
        "TermID": "006"
      }
    ],
    "RespMsg": "SessKey Expires|4/18/2019 7:29:47 AM",
    "SessKey": "B9F24903C3BA4770AE303032303541303032353437",
    "ThisUser": {
      "APILocationID": 2210,

Content-Type string required

Example: application/json

Accept string required

Example: application/json

AcctCode string optional

Account code that never changes

Example: EP911XXXX

Token string optional

Token that expires every 2 years

Example: 2148B239CF6846BDA5D141BF4A4CFBE8

ACH

Apply credit to an ACH transaction

post: https://easypay5.com/APIcardProcREST/v1.0.0/ACH/ApplyCredit

SessKey string required

A unique session key used for authentication in API calls. This key is generated upon successful authentication and must be included in all subsequent requests.

Example: A1842D663E9A4A72XXXXXXXX303541303234373138

Content-Type string required

Process payment with ACH annual consent

post: https://easypay5.com/APIcardProcREST/v1.0.0/ACH/ProcPayment

{
  "ConsentID": 21,
  "ProcessAmount": 5.1
}

{
  "ACHConsentAnnual_ProcPaymentResult": {
    "ErrCode": 0,
    "ErrMsg": "",
    "FunctionOk": true,
    "RespMsg": "APPROVED 67210748 TXID 000035",
    "TxApproved": true,
    "TxID": 72,
    "uniqueTranID": "16790131F349BCBA"
  }
}

SessKey string required

A unique session key used for authentication in API calls. This key is generated upon successful authentication and must be included in all subsequent requests.

Example: A1842D663E9A4A72XXXXXXXX303541303234373138

Content-Type string required

Example: application/json

Accept string required

Example: application/json

ConsentID integer optional

Example: 21

ProcessAmount number · float optional

Example: 5.1

Void an ACH transaction

post: https://easypay5.com/APIcardProcREST/v1.0.0/ACH/Void

SessKey string required

A unique session key used for authentication in API calls. This key is generated upon successful authentication and must be included in all subsequent requests.

Example: A1842D663E9A4A72XXXXXXXX303541303234373138

Content-Type string required

Card Operations

Process a Card Sale

Process a Refund

Process a refund to a settled charge

post: https://easypay5.com/APIcardProcREST/v1.0.0/CardSale/ApplyCredit

Use this call to process a refund to a settled charge. You will need the Transaction ID and the amount to be refunded.

SessKey string required

A unique session key used for authentication in API calls. This key is generated upon successful authentication and must be included in all subsequent requests.

Example: A1842D663E9A4A72XXXXXXXX303541303234373138

Consent Annual

Calculate surcharging or convenience fees Charge a stored card Create Annual Consent

Cancel a consent (Card On File)Modify an annual consent Create an annual consent with manual card entry

Calculate surcharging or convenience fees

post: https://easypay5.com/APIcardProcREST/v1.0.0/ConsentAnnual/CalcFees

This API call is for merchant accounts that are specifically configured for surcharge and/or convenience fee processing. Prior to charging a card on file, you may use this method to properly calculate the intended fees (Surcharging or Convenience fees ).

Fees will be calculated based on the merchant configuration and the card type itself. It is important to show the calculated fees at the point of sale so that a cardholder can reject the sale if they desire.

You can specify a Alternate MerchID rather than use the merchant record originally designated when you saved the card. A Value Of ZERO will use the original Merchant record.

Once you have determined your fees you can then call the method named : Charge Stored Card with Options to authorize the sale.

{
  "ConsentID": 7849,
  "Amount": 52,
  "AlternateMerchID": 0
}

{
  "ConsentAnnual_CalcFeesResult": {
    "ErrCode": 0,
    "ErrMsg": "",
    "FunctionOk": true,
    "RespMsg": "Fees calculated for CREDIT Card 4663XXXXXXXX2741",
    "Amounts": {
      "BaseAmt": 52,
      "Surcharge": 1.04,
      "TotalAmt": 53.04
    }
  }
}

SessKey string required

A unique session key used for authentication in API calls. This key is generated upon successful authentication and must be included in all subsequent requests.

Example: A1842D663E9A4A72XXXXXXXX303541303234373138

Content-Type string required

Example: application/json

Accept string required

Example: application/json

ConsentID integer optional

ID for consent associated with the merchant account

Example: 7849

Amount number · float optional

Base $ amount for which fees are to be calculated

Example: 52

AlternateMerchID integer optional

ID of the merchant to collect the payment funds. Use 0 for the merchant on consent.

Cancel a consent (Card On File)

post: https://easypay5.com/APIcardProcREST/v1.0.0/ConsentAnnual/Cancel

Use this call to Cancel a consent (Card On File). You will need the ConsentID in order to execute this method.

SessKey string required

A unique session key used for authentication in API calls. This key is generated upon successful authentication and must be included in all subsequent requests.

Example: A1842D663E9A4A72XXXXXXXX303541303234373138

Consent Recurring

Consent Subscription

Modify a consent subscription

Cancel a consent subscription

Cancel an existing subscription consent

post: https://easypay5.com/APIcardProcREST/v1.0.0/ConsentSubscription/Cancel

SessKey string required

A unique session key used for authentication in API calls. This key is generated upon successful authentication and must be included in all subsequent requests.

Example: A1842D663E9A4A72XXXXXXXX303541303234373138

Content-Type string required

International

Generate a receipt for an international transaction

post: https://easypay5.com/APIcardProcREST/v1.0.0/Intl/ReceiptGenerate

REFID will be the transaction ID ReceiptType will always be 23 for International

Consuming the Response The member named ReceiptHtml holds the receipt data Important you must replace all Unicode characters to consume clean HTML Example : CleanHtml = Regex.Replace(my, @"[^\u0000-\u007F]+", string.Empty);

SessKey string required

A unique session key used for authentication in API calls. This key is generated upon successful authentication and must be included in all subsequent requests.

Query

Account profile Batch logs Recurring consents Consent General Query Receipt Details Transaction Full Detail Voice Reconcile

ACH transactions Annual consent Retrieve full details of a recurring consent Recurring Schedules Transaction Search Transaction Receipt Enumeration values

Account profile

post: https://easypay5.com/APIcardProcREST/v1.0.0/Query/AccountProfile

{
  "AccountProfileQryResult": {
    "AccountProfile": {
      "AccountCode": "EP9116875",
      "AccountName": "EP DEV ACCT",
      "AutoSchedule": true,
      "AutoSettle": true,
      "AutoSettleHour": 0,
      "AutoSettleMinute": 0,
      "BatchReport": false,
      "DateCreated": "2024-12-01T11:19:01.000Z",
      "DateModified": "2024-12-01T11:19:01.000Z",
      "ID": 205,
      "IndustryCode": "",
      "TimeZone": "Dateline Standard Time",
      "TransReport": false
    },
    "ErrCode": 0,
    "ErrMsg": "",

SessKey string required

A unique session key used for authentication in API calls. This key is generated upon successful authentication and must be included in all subsequent requests.

Example: A1842D663E9A4A72XXXXXXXX303541303234373138

Content-Type string required

Example: application/json

Accept string required

Example: application/json

Receipt Details

post: https://easypay5.com/APIcardProcREST/v1.0.0/Query/ReceiptDetail

{
  "TxID": 12
}

{
  "ReceiptDetail_QueryResult": {
    "ErrCode": 0,
    "ErrMsg": "",
    "FunctionOk": true,
    "ReceiptInfo": {
      "AC": null,
      "AID": "A0000000031010",
      "ARC": "00",
      "AcctHolderID": 1,
      "CardHolder": "Sean Wood",
      "CardNumber": "1111",
      "CardType": "VI",
      "EndCustID": 12,
      "EndCustomer": "JOHN DOE",
      "EntryType": "MANUAL",
      "MerchAddress": "45 spring street",
      "MerchCity": "portland",
      "MerchDescrip": "Test Merchant 1",

SessKey string required

A unique session key used for authentication in API calls. This key is generated upon successful authentication and must be included in all subsequent requests.

Example: A1842D663E9A4A72XXXXXXXX303541303234373138

Content-Type string required

Example: application/json

Accept string required

Example: application/json

TxID integer optional

Transaction ID for which to retrieve the receipt details

Example: 12

Transaction Receipt

Retrieve a transaction receipt

post: https://easypay5.com/APIcardProcREST/v1.0.0/Query/TransactionReceipt

{
  "TxID": 2,
  "ReceiptType": 2
}

{
  "TransactionReceiptQryResult": {
    "ErrCode": 0,
    "ErrMsg": "",
    "FunctionOk": true,
    "ReceiptHtml": "html",
    "RespMsg": "Successfully Returned Transaction Receipt Markup"
  }
}

SessKey string required

A unique session key used for authentication in API calls. This key is generated upon successful authentication and must be included in all subsequent requests.

Example: A1842D663E9A4A72XXXXXXXX303541303234373138

Content-Type string required

Example: application/json

Accept string required

Example: application/json

TxID integer optional

The unique identifier for the transaction

Example: 2

ReceiptType integer · enum optional

The type of receipt

1: Transaction

Voice

Retrieve voice settings

post: https://easypay5.com/APIcardProcREST/v1.0.0/Query/VoiceSettings

SessKey string required

A unique session key used for authentication in API calls. This key is generated upon successful authentication and must be included in all subsequent requests.

Example: A1842D663E9A4A72XXXXXXXX303541303234373138

Content-Type string required

Enumeration values

Methods related querying general information such as enum values

post: https://easypay5.com/APIcardProcREST/v1.0.0/Query/Enum

SessKey string required

A unique session key used for authentication in API calls. This key is generated upon successful authentication and must be included in all subsequent requests.

Example: A1842D663E9A4A72XXXXXXXX303541303234373138

Content-Type string required

Reconcile

Reconcile transactions

post: https://easypay5.com/APIcardProcREST/v1.0.0/Query/Reconcile

The reconcile Query is designed to be called at a specific periodic interval, perhaps once per day. We will return all the unique transaction IDs encountered during that interval. The query allows you to reconcile this list with data you have gathered during cardholder data interactions such as PayForm or Verifone Activity. If you find that a particular transaction is missing in your database you can call the TRANSACTION FULL DETAIL to consume any missing information.

You may specify either Credit Card or ACH transactions to be returned in the Query ( see qType parameter ) use "CARD" or "ACH". When choosing dates you can consider the StartDate to be Included in your data request however the EndDate will not. You will receive all data which runs up to but not including the end date. For example choosing the following dates will provide data for a single day on the calendar: "2024-12-01" "2024-12-02"

IMPORTANT: Do not call this method more than once a day. Excessive queries can cause your endpoint to be blocked. The max date range for this method is 31 days. The max records returned is 20,000. If you notice that the NumRecords returned equals 20000 then this means you have maxed out your query and you should use a smaller date range.

Receipt

Generate a transaction receipt

post: https://easypay5.com/APIcardProcREST/v1.0.0/Receipt/ReceiptGenerate

Use this call to request receipt details in HTML format for a particular TXID (Transaction ID). This method works for card on file documents as well as transaction receipts. You will need the TXID (Transaction ID) as well as a receipt type and a targeted recipient ( Customer or Merchant ).

The following will provide a customer receipt for TXID 123:
{ "REFID": 123, "ReceiptType": 1 (Sales Receipt) "Recipient": 1 (Customer Copy) }

Important you must replace all Unicode characters to consume clean HTML

Example : CleanHtml = Regex.Replace(my, @"[^\u0000-\u007F]+", string.Empty);

Recurring Schedule

Cancel a recurring payment schedule

post: https://easypay5.com/APIcardProcREST/v1.0.0/RecurringSchedule/Cancel

{
  "SchedID": 10
}

{
  "RecurringSchedule_CancelResult": {
    "ErrCode": 0,
    "ErrMsg": "",
    "FunctionOk": true,
    "RespMsg": "Successful Cancel of SchedID 10 For $10.00 On 6/23/2019",
    "ScheduledPayment": {
      "AcctHolderID": 782,
      "AcctNo": 119,
      "ConsentID": 396,
      "ConsentType": "S",
      "DueOn": "2024-12-01T11:19:01.000Z",
      "ID": 282,
      "LastName": "Draper",
      "MerchID": 1,
      "OfTotalPayment": 100,
      "OfTotalPayments": 10,
      "PaymentAmt": 300,
      "PaymentNum": 1,

SessKey string required

A unique session key used for authentication in API calls. This key is generated upon successful authentication and must be included in all subsequent requests.

Example: A1842D663E9A4A72XXXXXXXX303541303234373138

Content-Type string required

Example: application/json

Accept string required

Example: application/json

SchedID integer optional

The unique identifier for the schedule to be canceled

Example: 10

Modify a recurring payment schedule

post: https://easypay5.com/APIcardProcREST/v1.0.0/RecurringSchedule/Modify

{
  "SchedID": 10,
  "PaymentAmount": 10,
  "DueDate": "2023-07-10T00:00:00.000Z"
}

{
  "RecurringSchedule_ModifyResult": {
    "ErrCode": 0,
    "ErrMsg": "",
    "FunctionOk": true,
    "RespMsg": "Successful Reschedule of SchedID 10 For $10.00 On 7/10/2023",
    "ScheduledPayment": {
      "AcctHolderID": 782,
      "AcctNo": 119,
      "ConsentID": 396,
      "ConsentType": "S",
      "DueOn": "2024-12-01T11:19:01.000Z",
      "ID": 282,
      "LastName": "Draper",
      "MerchID": 1,
      "OfTotalPayment": 100,
      "OfTotalPayments": 10,
      "PaymentAmt": 300,
      "PaymentNum": 1,

SessKey string required

A unique session key used for authentication in API calls. This key is generated upon successful authentication and must be included in all subsequent requests.

Example: A1842D663E9A4A72XXXXXXXX303541303234373138

Content-Type string required

Example: application/json

Accept string required

Example: application/json

SchedID integer optional

The unique identifier for the schedule to be modified

Example: 10

PaymentAmount number · float optional

The new $ payment amount for the schedule

Example: 10

DueDate string · date optional

The new due date for the schedule

Process scheduled payments

post: https://easypay5.com/APIcardProcREST/v1.0.0/RecurringSchedule/ProcessScheduledPayments

SessKey string required

A unique session key used for authentication in API calls. This key is generated upon successful authentication and must be included in all subsequent requests.

Example: A1842D663E9A4A72XXXXXXXX303541303234373138

Content-Type string required

Settlement

Execute batch settlement for all transactions

post: https://easypay5.com/APIcardProcREST/v1.0.0/Settlement/ExecuteBatch_All

{
  "MerchID": 1
}

{
  "Settlement_ExecuteBatch_AllResult": {
    "BatchResult": {
      "BatchClose": 720191352,
      "BatchLogID": 103,
      "BatchNetAmount": 10,
      "BatchNum": 3,
      "BatchOpen": 720191352,
      "BatchTransCount": 1,
      "Code": "A",
      "RemainingUnsettled": 0,
      "ResultText": "OK 003 0720 0000                ",
      "TxLock": "7A639CD720CE4B14"
    },
    "ErrCode": 0,
    "ErrMsg": "",
    "FunctionOk": true,
    "RespMsg": "Successful Settlement : OK 006 0808 0000                ",
    "SettlementApproved": true

SessKey string required

A unique session key used for authentication in API calls. This key is generated upon successful authentication and must be included in all subsequent requests.

Example: A1842D663E9A4A72XXXXXXXX303541303234373138

Content-Type string required

Example: application/json

Accept string required

Example: application/json

MerchID integer optional

The merchant identifier

Example: 1

Help

Customer Support

We are here to assist you with Number integration. Our dedicated support team is ready to answer all technical and business-related questions. You can count on our support 24/7.

Use one of the recommended contact options:

Integration Options

Learn about how you can integrate with Number

Before you start using our services, you'll want to decide which type of integration is most suited to your business case. We provide a plethora of ways to start using our services:

REST API
Mobile SDKs for Android and iOS
PayForm and legacy widgets
The Virtual Terminal web application
Custom desktop applications
Win service and DLL

You don't have to limit yourself to one type of integration. Many integrators use our PayForm to collect the cardholder data, and then use our API for the rest. The Virtual Terminal can also be used for various functions such as processing payments, creating card-on-file plans (consents), and generating reports. You can find more details about each integration in the next few sections.

Before you read about the specific integration options, we recommend having a look at the section below to help you clarify which options are relevant to your unique case.

PCI Compliance

What is PCI DSS?

PCI compliance refers to adherence to the Payment Card Industry Data Security Standard (PCI DSS), which is a set of security standards related to processing, storing, and transmitting credit card information. The PCI DSS was developed by the Payment Card Industry Security Standards Council (PCI SSC), which was founded by major credit card companies like Visa, MasterCard, American Express, Discover, and JCB.

Key aspects of PCI compliance include:

Maintaining Secure Networks and Systems: Installing and maintaining a firewall configuration to protect cardholder data and not using vendor-supplied defaults for system passwords and other security parameters.
Protecting Cardholder Data: Companies must protect stored cardholder data and encrypt transmission of cardholder data across open, public networks.

PCI compliance helps protect cardholder data from theft and fraud, ensuring consumer trust and avoiding fines and penalties associated with non-compliance. Businesses of all sizes that handle credit card information are required to comply with PCI DSS.

Integration choice based on compliance

If you are not already handling cardholder data by yourself, Number can do that for you.

Depending on whether or not you are handling the card holder data under your own documented PCI level one compliance program, you'll want to use different types of integrations.

If you have your own PCI level one compliance program umbrella, you may use our APIs for all types of payment activities, including authorization of cards, issuing credits, reversal, reports, etc.
Otherwise, you can use our PayForm web widget and other applications served under our PCI Level One platform to collect cardholder data, and use our API for any and all other payment-related activities.

REST API

The REST API will allow you to enable integration of Number payments with external applications, allowing for full automation and a high degree of customization.

They allow a variety of functions:

Processing payments / voids / credits / settlements,
Running queries and reports,
Returning receipts and documents for signature,
Creating / modifying / processing payment plans.

It's important to note that some API functionality will require you to collect cardholder data, such as , and that requires you to be PCI Level 1 compliant. You can overcome this by using our PayForm to collect all cardholder data securely.

You can read more about implementation in the API integration guide:

Mobile SDKs

The mobile SDKs will allow you to integrate Number payments services into any Android and iOS application using the prebuilt payment UI components. Similar to PayForm, those components will allow you to collect cardholder data and process payments in a secure and PCI compliant way.

In addition to the native Android and iOS SDKs, we offer a React Native wrapper which can be used to build a cross-platform app.

If you need to integrate Number payments with a mobile application, we recommend using the SDKs.

You can read more about implementation in the SDK integration guides:

PayForm and legacy widgets

A PayForm is the most convenient means of collecting cardholder data. By using our builder tool or our API, you'll be able to set the design and behavioral aspects of the form and we'lll return a URL which loads it into the view. The form will then use webhooks to POST the realtime data to the site of your choice.

Once the cardholder data is collected, you can use other integrations, such as our APIs or the Virtual Terminal, to process consents, credit, void, and query transactions.

We also have a widget as a legacy option to the PayForm. With this widget, users will enter their cardholder data directly into the Number platform, and your system can be updated in realtime. If you're just starting, we suggest using the PayForm as our modern option.

We recommend using the PayForm to collect all cardholder data when integrating with web applications as it's secure, easy to get started, and offers a lot of customization.

You can read more about implementation in the integration guides:

Virtual Terminal

The Virtual Terminal (VT) is a web application which you can access through your browser. It provides all types of credit card processing functionality:

Authorizations,
Voids / credits / settlements,
Reporting,
Payment plans (recurring / subscription consent),

The VT is the fastest way to start trying out our payment services. Otherwise, it's ideal for businesses processing payments over the phone or at sales points lacking a physical terminal.

You can read more about the Virtual Terminal in the user guide:

Our custom desktop application

We also have a custom desktop application which can be convenient in an office setting to collect card present payments. This application offers much of the same functionality as the Virtual Terminal. As opposed to the Virtual Terminal, the desktop app only requires you to authenticate once a day to keep your session.

The application interfaces with VeriFone card readers. These devices accept EMV chip and contactless cards in addition to the usual card swipe and manual entry.

to learn more about custom desktop applications.

Win service and DLL

If you wish, you can take advantage of our end-to-end encryption model used with the Verifone card reader and build around it by using our Windows service or referencing our Dynamic Link Library. They channel requests through our API and responses can be consumed at the client software level. This way, you can develop your own workflow and displays.

You can read more about integrating with Verifone in the integration guide:

Card Sales and Consent

Learn to make credit card sales and collect consent with Number

To make sales or collect consent when a card is present using Number, you have several options:

Integration with a Verifone card reader

You can use Verifone card readers. They are secure devices that connect to your computer via USB. They encrypt cardholder data during transmission to ensure security.

USB card reader through the Virtual Terminal or our desktop app

When you have a USB card reader connected to your machine, you can log into the Virtual Terminal to make card present sales and to collect consent.

We also have a custom desktop application which can be convenient in an office setting to collect card present payments. It offers similar functionality to the Virtual Terminal.

Custom integration with our REST API

Our REST API offers methods for handling card present transactions.

If you have your own PCI level one compliance program, you may write your own custom code calling our APIs to collect card present payments and consent. You can read more about PCI compliance in the short section of our guide.

Verifone integration

There are a few approaches to integration, You can either use the browser-based interface option or the Desktop integration with SDK .

For an in-depth tutorial on how to integrate and use your Verifone card reader with Number, see our integration guide.

Before you start, you'll need to download the Verifone Windows service to your machine, connect your card reader device to a free USB port, allow it to initialize, extract the archive with the service and run the EXE as an administrator. After the installation is complete, reboot the system.

You can issue commands to the service by calling https://localhost:8031 from your website.

Verifone card present sales

Here's an simplified example of how you can invoke the service for a card present sale:

Here's an simplified example of how you can invoke the service to collect annual consent:

Virtual Terminal or desktop application

When you want to use your Verifone with the Virtual Terminal, you have to first install the very same Windows service that is used when doing a Verifone browser-based integration. After installation, to get the card reader features activated.

To learn more about using the Virtual Terminal, see the user guide.

Read more about using our custom desktop application for sales in the guide or to get access.

Virtual Terminal card present sales

When you visit the Virtual Terminal, log in and expand Credit Cards in the navigation on the left. You'll see options for a sale, an EMV sale, authorization, forced auth, and adjustments.

As long as your USB card reader is connected to your machine, it will seamlessly integrate with the Virtual Terminal for card present transactions.

When you visit the Virtual Terminal, log in and expand Consents in the navigation on the left. You'll see options for annual consent, EMV annual consent, and one-time consent. You can also expand the Recurring tab to find options to create recurring consent, EMV recurring consent, and subscription consent.

As long as your USB card reader is connected to your machine, it will seamlessly integrate with the Virtual Terminal for card present transactions.

REST API integration

Our APIs are useful for any Integration as you can apply a credit, void, query, charge a stored card etc. For integrators who are PCI Level one compliant you may also pass cardholder data directly through the API. Most integrations will use our PayForms to collect Cardholder data while the API will be used for all remaining activity.

To learn more about our APIs, see the integration guide.

When you scan the credit card and collect the track data alongside the other payment details, if using the REST API, prepare the HMAC secured header like shown in quickstart guide, and encrypt the card number using our RSA certificate.

Follow the instructions in the API reference to prepare and handle the request.

API card present sales

You can use the following API operations:

For the REST API, use

You can use the following API operations:

For the REST API, you can use and .

To make credit card sales and collect consent using Number when you want to enter the card details manually, you have the following options:

You can configure and customize our PayForm widget and redirect your users to a separate page with the form or embed it as an IFrame in your existing web application.

The PayForm is designed to be a highly flexible and secure payment form for your users. To start collecting payments and consent with the PayForm, you'll want to use our builder tool for configuration, then our REST API to generate a payment URL.

Learn more about how to configure and use the PayForm in the guide.

You can read about configuration specifics in the section of our full PayForm guide. For the purpose of this tutorial, you can follow the example below; we'll briefly explain each configuration step.

PayForm manual card sale

In the example below, the PayForm has been setup for an instant card payment.

Visible and read-only fields

The cardholder will need to provide their first and last names, full address, email, and click a checkbox to agree to pay and give their permissions to receive an email.

Additionally, they'll see the amount field, but it'll be read-only.

The JSON will look like the following:

This JSON can be used to make a REST API request to generate the actual payment form.

You may re-use this JSON to generate the same type of form for multiple different users. You may also want to dynamically configure values like the amounts from your code.

To generate a PayForm, make a request to .

If you include a valid session key, the PayForm will be accessible under the PaymentUrl included in the response. You can embed it into your site or redirect the user to the page.

Once the user fills out and submits the form, we'll handle the payment.

If you want to handle the query string when redirecting back to your website to store the transaction ID in your database, read the section of our full PayForm guide.

To use the PayForm to save a card on file, follow the steps in , change the transaction type to collecting cardholder data, and skip the amount field.

You may also collect an instant payment and consent at the same time by choosing the combo widget as your transaction type.

Virtual Terminal or desktop application

The Virtual Terminal is a web application that allows you to manually enter credit card details and process transactions through your browser.

To learn more about using the Virtual Terminal, see the user guide.

Read more about using our custom desktop application for sales in the guide or to get access.

Virtual Terminal manual card sale

When you visit the Virtual Terminal, log in and expand Credit Cards in the navigation on the left. You'll see options for a sale, an EMV sale, authorization, forced auth, and adjustments. Follow the instructions and manually enter the cardholder details to make a sale.

Using the Virtual Terminal, you can create annual, one-time, recurring, and subscription consents. Log in and expand Consents and Recurring tabs on the left side of the screen. Choose the type of consent you're interested in and follow the instructions to manually enter the cardholder details and store a card on file.

Android / iOS SDK integration

If you are developing an Android or iOS application, you can utilize our SDKs to charge credit cards and collect consent manually by having users enter their own details.

We recommend following the and guides to learn how to integrate Number with your mobile applications.

Mobile manual card sale

The relevant methods are described in section of the guide and section of the guide.

REST API integration

If you wish to have more control over the integration and you are PCI Level 1 compliant, you can try using our APIs. They provide methods for all payment types available using our other services, including manual card sales and collecting different types of consent.

To learn more about our APIs, see the integration guide.

After authenticating, when you collect cardholder data alongside the other payment details, if using the REST API, prepare the HMAC secured header like shown in quickstart guide, and encrypt the card number using our RSA certificate. Follow the instructions in the API reference to prepare and handle the request.

Manual card sale

You can use the following API operations:

For the REST API, use .

You can use the following API operations:

For the REST API, use for annual consent and for recurring consent.

Virtual Terminal

Getting started with Virtual Terminal for Number

The Virtual Terminal is a web application that provides all types of credit card processing functionality. The VT is the fastest way to start trying out our payment services.

When you log in to the Virtual Terminal, you are brought to the home screen. The number of open transactions and scheduled payments due display at the top of the screen. Your default merchant and user roles are listed just below, along with the expiration date of your password.

Payments

Instructions on how to manage various payments using the Virtual Terminal.

Before you start, you may want to read about using your Verifone device with the Virtual Terminal in the guide.

Non-EMV payments

Make non-EMV manual sales using the Virtual Terminal.

Click the Credit Cards tab on the left side of the screen, then Sale. Manually enter all of the information from your keyboard, and enter the $ amount to be charged.

A guest ID or a service description can also be added here and searched for later. The ID will also print on the receipt, and the service description will print on the settlement report.

EMV payments

Make EMV payments using the Virtual Terminal.

Click the Credit Cards tab on the left side of the screen, then on Sale-EMV. You will then need to click on Insert Chip or Manual Card Entry.

Clicking on Insert Chip will prompt the end-user or customer to insert or tap their card for contactless payments. For Manual Card Entry, the end user must enter the full card number, expiration date, and CVV code by pressing the green enter button on the Verifone after each entry.

Surcharging

Surcharge and convenience fees are automatically calculated during a credit card sale, both manual entry and EMV, as well as when charging an existing card on file.

The surcharge / convenience fee is automatically calculated based on the percentage set in the Client Admin Portal and the card type used. The Virtual Terminal will also ensure that fee does not go over the card brand rules of 3%.

Users have the option to waive the fee on any transaction if required. The fee can be waived before processing by checking the Waive Fee box on the form.

The receipt will detail the charge amounts including the base amount, fee, and total amount charged. Rules require that the fee amount is visible to the customer. In addition to the receipts, the Virtual Terminal reporting and detail views show the fee as part of the total amount.

Create consents

All consent types allow a card to be charged without the card or customer being present. Consents can be created by swiping the card or manually entering the information.

A consent receipt is always created by the system for your customer to sign. We encourage your office to get signatures for consents whenever possible.

An email address can be added to the consent so your customer will receive a receipt when the consent has been used.

Annual and one-time

Creating annual and one-time consents allows your office to charge a card at a later date. This can be useful in situations where you expect a balance to be due after services have been provided.

An annual consent can be used multiple times, and a one-time consent can only be used once.

Both annual and one-time consents are valid until the card expires or 365 days have passed.

Click the Consents tab on the left side of the screen, then Create Annual Consent, Create Annual: EMV, or Create One-Time Consent depending on the type of consent you need and payment method.

Annual consents require that a max charge be determined as a limit per transaction. This can be any $ amount determined by your office.

An email address can also be added to the consent so your customer will receive a receipt when the consent has been used.

Fixed recurring

Creating a fixed recurring consent allows your office to set up a payment plan with your customer. This can be useful in situations where your customer has an outstanding balance due.

Fixed recurring consents can be setup for any length of time.

Click the Recurring tab on the left side of the screen, then Create Recurring Consent or Create Recurring: EMV based on the payment method.

An email address can be added to the consent so your customer will receive a receipt

Subscription

Creating a subscription consent allows your office to set up a re-occurring payment indefinitely. This can be useful in situations where your customer makes a regular donation or payment to your organization.

The subscription consent end date is always automatically set to the card expiration date.

Click the Recurring tab on the left side of the screen, then Create Subscription.

Subscription payments can be processed manually or automatically depending on your preference. You can change the payment amount as well as the scheduled dates for your subscription consent.

To alter the schedule, you will modify the Payment Adjust Date. The system will discard the previously scheduled payment plan and calculate a new one. Only those scheduled payments for today and beyond will get processed, and it will not attempt to process payments for dates in the past.

You can also place a subscription on hold. This will pause all processing until the hold is released. Once released, payments will resume for all present and future payments as calculated using your dates and amounts.

The consent list is where you will manage your consents after they have been created. The query filter can be used to search your consent list.

Click the Reports tab on the left side of the screen, then Consents.

In the Consent Operations box right above the table, there are several options available to help you manage your consents. The availability of each option will vary depending on whether the selected consent is annual or recurring.

Edit

The edit screen allows you to add or change the email address associated with consent, update the billing zip code and expiration date, add or change the reference ID and service description.

Receipts

Allows you to reprint the consent agreement. You can choose between the customer, merchant, and dual receipt options.

Scheduled payments

The scheduled payments view is where you will view and manage all scheduled payments.

Click the Scheduled option on the left side of the screen.

Schedule Operations

Run fixed recurring consents and subscriptions.

Scheduled payments can also be run automatically on the day they are due. and we'll turn this feature on up for you.

Filter the consents you want to run by date range and consent type. Once you have the consents you want to charge filtered, you can click Process All to process all payments due. You can also individually select consents and run them by clicking Process Selected.

The option to Reschedule or Cancel Payment are also available.

Failed Payments

If a customer’s card is declined, you will receive a notification report.

Payment History

Displays a history of payments run on a particular consent through the Scheduled Payments option.

Transaction list

The transaction list is where you will view and manage the transactions.

Click the Reports tab on the left side of the screen, then Transactions.

Transaction operations

In the Transaction Operations box right above the table, there are several options available to help you manage your transactions.

Void

Voids can be performed the same day as the transaction before settlement.

Receipts

Reprint the receipts. You can choose between the customer, merchant, and dual receipt options.

Transaction filter

Filter transactions based on the merchant the transaction was processed under, the date range, transaction status, and transaction type.

Transaction status and type filters

For filtering by transaction status and transaction type, see the table below.

TxStatus

TxType

Transaction search

Search your database, create reports based on results, void, credit, and reprint receipts.

Search for

Find the search value in a specific field by using the Search for a dropdown.

Search field type

Search value

The value to search for in the specified field.

Search type

Choose the desired comparison type for search.

Settlements

View and manage the settlements.

Click the Settlement option on the left side of the screen.

Manually settle transactions.

Select the appropriate merchant account.

Select individual transactions, and click Settle Selected. Click Settle All to settle all open transactions, or click Preview Batch to see what will be settled.

Batch history

Displays a list of your settlements and allows for reprinting of batch reports.

Click on the Reports tab on the left side of your screen, then Batch History.

Miscellaneous

In the upper right-hand corner of the screen, there is a menu of miscellaneous operations.

My Settings

Update your name, email, cellphone number, and change your password

Lockouts

In order to protect our client’s information, it is necessary for us to lockout users who cannot provide correct credentials. A lockout will occur if incorrect credentials are entered 6 times in a row.

There are two types of lockouts:

User lockout occurs when a user entered their password incorrectly for 6 successive attempts.
Endpoint lockout causes your entire office to be locked out because the username entered was unknown to our system, and used for 6 successive attempts.

If you are experiencing problems authenticating, contact your administrator to reset your credentials. We recommend to do this before the 6th attempt which could cause a lockout.

If you do experience a user lockout, you will need to follow these steps to continue:

Get new credentials

Obtain new or updated credentials from your administrator

If you do experience an endpoint lockout, you will first need to need to call the to get the lock removed, then follow the instructions for a user lockout.

Expired passwords

As an additional security precaution, passwords expire after 4 months. You can see your password expiration date every time you log into the Virtual Terminal.

You may choose to change your password as often as you wish, however you must change your password every 4 months at a minimum. Entering an expired password 6 times in succession will cause a user lockout as described above.

Verifone

Getting started with Verifone for Number

The Verifone card readers are small hand-held devices. They communicate with your computer on a USB port. A chip transaction is comprised of about a dozen transmissions between the host (your computer) and the device, and then finally to the Number cloud platform.

Using the Verifone card readers offers a highly secure method of collecting cardholder data.

Cardholder data is encrypted within the device itself, and remains encrypted as it travels across the Internet to our PCI Level One Compliant processing platform.

When a merchant supports a Verifone card reader, it helps eliminate chargebacks for transactions which were run through the device.

PCI SSC SSF

Software Security Framework (SSF) is a re-working of the existing PCI standard PA DSS. The PA DSS has been retired since June 30, 2021. Number's "Aspen 3.1" is the first application to achieve the PCI Councils SSF certification, and it provides an end-to-end encrypted solution.

Software options

Currently, we offer three different options for collecting payments with the Verifone card readers, all of which require a Windows OS on the host computer.

Standalone desktop application (upon request)

This application has automatic updates and allows you to collect payments, create card-on-file and payment plans, process a card-on-file, void or credit, settle transactions, and do reporting with an option to export to a PDF.

Browser-based interface

We developed a Windows service which uses Cross-Origin Resource Sharing (CORS) to communicate with the browser. The Win service will return a simple XML response for each transaction directly to the HTML/PHP/ASP.NET page for consumption by the host application.

As an integrator, this allows you to write simple client-side scripts within your own web applications to initiate transactions with a local Verifone. You can also use this service with our Virtual Terminal to avoid writing any code.

Requirements

There are 2 categories of integrations which require two different sets of files

Browser-based - install our Win service which contains all your dependencies, including the drivers and console installer.
Desktop-based - install our SDK, then use separate installers for drivers and a custom event log.

Desktop application

If you wish to use the standalone desktop application for Verifone, for installation files and instructions.

Browser-based installation

For any browser-based Implementation using the Verifone, you will need to install the local win service. This includes our Virtual Terminal implementation as well as your own custom web applications.

To Begin: Download the compressed archive:

To install the Win service:

Connect your device to a free USB port.

Allow the device to initialize.

Extract the above archive to a location of your choice.

The above installation package does the following:

Installs USB drivers for the Verifone.
Creates a custom event log with Windows named EPmiddleware.
Installs a certificate which encrypts data between the browser and the Windows service.
Installs the EasyPay Verifone MiddleWare E2E 1042 Service which listens on port 8031.

Your website can now issue commands to the Win Service as is demonstrated using the sample site:

You can download the entire site here:

To run the Verifone demo website, you must have the Verifone Windows service installed.

Virtual Terminal

You can use our Virtual Terminal together with the Windows service. It has built-in support for Verifone. This way, you won't have to build your own UI or write any code. After installing the service, to have this feature activated.

You can read more about using the Virtual Terminal in the guide.

Requesting a transaction from your custom web application

You will find a script file named EasyPayVerifone.js in the sample VeriFone website provides the following functionality:

EMV sale only
EMV sale and save card
Manual sale (keyed entry) sale only
Manual sale and save card

You can call these functions as follows:

Creating your first EMV transaction

In the script file named EasyPayVerifone.js you can inspect the function named EMVSaleCombo():

EMVSaleCombo(SaveCard)

It expects the following objects

SaveCard ( true / false)
SessionKey ( string )
AccountHolder ( Json )
EndCustomer ( can be the same as Accountholder )

The SessionKey is obtained by using our API to Authenticate. Your Server can pass this down to your client side script.

The AccountHolder object looks like this. Note the embedded address object:

The End Customer object is identical to the Accountholder object . You may not have two objects so you can set both to the same value.

The PurchaseDetails object provides two user defined fields and a service description for your use and this object looks like this:

The Amount object supports both a simple number such as "103.41" or an object such as the following:

If you don’t plan to collect processing fees then you can just send a simple numeric value.

Once you have compiled all Json Object data you make your call to the local windows service as is outlined in the EasyPayVerifone.js script file.

Here is a sample URL GET request:

Resetting The Device

The red Button on the Verifone can be used to Cancel the current operation and also to setup for the Ready State. Your software will be notified of the Reset should this Occur.

You can also call the function named UnlockVerifone(); which will reset both the software and the hardware so that you can once again enter the ready state.

If you ever send a command to the Verifone Middleware while it is still processing the previous one, it will respond with an error stating that is it BUSY. In the rare situation where the Middleware remains Busy for an unreasonable amount of time you can issue the UnlockVerifone(); command in order to return the device to the ready State. You can also press the red Button on the device 2 times to enter the ready state.

If you continue to receive a Busy response from the middleware, but you don't believe that waiting will yield productive results, you may use the unlockVerifone function to return the device to Ready state.

Middleware response types

For browser type Verifone operations, the middleware provides a response object in XML format. This object can be de-serialized or can be consumed as XML. Currently, there are two response object types:

WidgetArgs - sale response when requesting an authorization for a non-zero dollar amount, with the option to save the card;
WidgetArgs2 - consent response when requesting to only save the card.

Consuming the sale response

It is important to consume the WidgetArgs response in a particular order, starting with TxEventTyp.

TxEventTyp string

The type of event that occurred during the transaction, indicating success or failure.

Values: TxApproved, TxDecline, TxReversed, PreSaleDeviceCode, PostSaleDeviceCode, TimeOut, AspenError, AuthFail, FunctionFail, Exception.

Here are actions to take for each possible value of TxEventTyp:

TxApproved

The sale was approved by the issuer. You should examine and store these values:

TxID - the unique ID of the transaction; needed to refund or void the transaction.
TxnCode - the transaction approval code.

It is important to consume the WidgetArgs2 response in a particular order, starting with ConsentEventTyp.

ConsentEventTyp string

The type of event that occurred during the save card on file operation, indicating success or failure.

Values: ConsentSuccess, ConsentFailed, PreConDeviceCode, PostConDeviceCode, TimeOut, AspenError, AuthFail, FunctionFail, Exception.

Here are actions to take for each possible value of ConsentEventTyp:

ConsentSuccess

The consent was created and card was saved successfully. You should examine and store ConsentID to be able to charge the customer later.

ConsentFailed

The consent was not created. Examine ErrCode and ErrMsg for more information.

Number Verifone SDK

Important : You can not run both the Verifone Middleware and the Verifone SDK together at the same time. Both packages will need to have control over COM 9 so only one can be active at one time.

Installation

For you to directly interface with the Verifone using our SDK, you will need the Verifone drivers with the custom logging package, and the SDK reference files:

When installed, the first component will provide USB drivers and create a virtual COM 9 port. In addition, it will add a unique event log to the existing windows event log collection.

To install the first component, please do the following:

Connect your Verifone to the USB port which you plan to utilize.

Wait until the device is fully initialized.

Download and extract the ZIP file named Setup_USB_log.zip to the location of your choice.

To use the SDK, you only need to directly interface to the file named EP.Enterprise.Vx820.dll. The other files are dependencies. Make sure to extract all 4 of the files to the location of your choice.

Number has developed a sample executable program using the SDK which allows you to authorize cards, save cards, and create payment plans:

Sample SDK Program

Initially you will need the following to begin processing cards

Number URL Endpoint ( API URL )
Account Code
Token

For testing you can use the default URL supplied but it is important that you consult with Number personnel to determine the best endpoint prior to going live. Your Account code and Token will be supplied to you for your sandbox account.

EMV Sale

Once you have authenticated you can proceed to the SALE page.

Take Notice of the MERCHID field as each Number Account can have one or more merchant records associated with it. For Live accounts you will be provided a deployment form which identifies these along with their identifier {1,2,3} etc.

For a typical Chip transaction, you only need to specify an amount and press INITIATE CHIP. The device should now prompt you to insert the CHIP. If you check the SAVE CARD checkbox then Number will VAULT the card details after the successful sale and return a CONSENT ID which you can use to authorize the card directly using our API at a later time. If you want to KEY IN the card details directly into the VeriFone, you will enter Account Holder Information then press INITIATE MANUAL TRANSACTION.

Programming Considerations

To reference the SDK

using EP.Enterprise.Vx820Lib;

Important : manage only one single instance of the class ( this allows you to operate on the COM 9 port )

private EP_Verifone_Mod EPVerifone;

Here are some steps required prior to doing a card authorization

Now you can initiate a transaction

Wait for your transaction to complete and event will fire

For additional coding samples including creating recurring payment plans please refer to the sample SDK program

Managing the Workflow

Once you initiate a transaction the EPVerifone class will set the DeviceIsBusy flag to True. make sure you monitor this flag before attempting another transaction. EMV transactions can take time and you will expect the On_Device_Msg Event to Fire to alert you of the Results. If for some reason the DeviceIsBusy flag stays true for an unreasonable amount of time you should issue the UnLockAndReset(ref ErrStr) command which will reset both the SDK Software and the Verifone Device in order for you to once again enter the Ready State. There is also a Red Button on the Verifone device which you can press two times to reset the process and fire the On_Device_Msg Event.

Custom Windows event log

After installing all the dependencies for either the SDK or the browser-based approach,, you will notice a new Windows event log has been registered named EPmiddleWare.

This event log stores information about processed transactions as well as any errors encountered, and serves as a powerful troubleshooting component.

With the Verifone Windows event log installed, a merchant can export the log and send it to Number if any unexpected behavior is encountered.

Verifone power settings

Both the middleware service and the SDK will attempt to maintain a continuous connection to the Verifone device. If your hardware is suspended or enters sleep, this can cause issues. To avoid these, please make sure to modify your USB power settings.

Windows 10 and Windows 11

For Windows 10, you'll need to go to Control Panel > Power Options > Edit Plan Settings.

On Windows 11, open Control Panel > Hardware and Sound > Power Options > Edit Plan Settings.

Go to Advanced power settings and change the USB settings to disable USB selective suspend for your active power plan.

When using the Verifone, make sure that your machine is running the power plan with the modified settings. All power plans have separate power settings.

If you don't see the USB power settings on your machine, you might need to expose them.

Run the Command Prompt as an administrator.
Type the command below you into the elevated command prompt, and press Enter:

NUMBER - Development Portal

Home

Embedded Payments Starts Here

Get Your Business Started

Implementation timeline

Documentation

Developer Quickstart

Authentication

Basics

Querying and Filtering

REST API

Example

Virtual Terminal

Getting Started

Basics

API Input Validation

Testing Considerations

Responses

Testing

Resources

Tools and Downloads

API

REST API downloads

Software Requirements

Computer specifications

Operating systems

Browsers

API Reference

REST API

Authentication

ACH

Apply credit to an ACH transaction

Process payment with ACH annual consent

Void an ACH transaction

Card Operations

Process a Refund

Consent Annual

Calculate surcharging or convenience fees

Cancel a consent (Card On File)

Consent Recurring

Consent Subscription

Cancel a consent subscription

International

Query

Account profile

Receipt Details

Transaction Receipt

Voice

Enumeration values

Reconcile

Receipt

Recurring Schedule

Cancel a recurring payment schedule

Modify a recurring payment schedule

Process scheduled payments

Settlement

Execute batch settlement for all transactions

Help

Customer Support

Use one of the recommended contact options:

Developer Quickstart

Get Your Business Started

Implementation timeline

Home

Embedded Payments Starts Here

Integrate Number

Serv﻿ices

Supported features

Get your business started

Resources

Software Requirements

Computer specifications

Operating systems

Browsers

Consent Annual

Consent Subscription

Card Operations

API Input Validation

Testing

Basics

Services