Card Sales and Consent

Card present sales and consent

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

Verifone integration

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

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:

Verifone card present annual consent

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, contact the Number support team to get the card reader features activated.

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.

Virtual Terminal card present consent

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.

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 Authentication 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 Process a Card Sale

API card present consent

You can use the following API operations:

• For the REST API, you can use Create Annual Consent and Create Recurring Consent.

Manual card sales and consent

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

PayForm widget

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.

You can read about configuration specifics in the PayForm builder 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.

The JSON will look like the following:

{
  "InitParams": {
    "MerchID": 1,
    "WTYPE": "PF",
    "PostURL": "",
    "RedirectURL": "https://yourwebsite.com/success",
    "REF_ID": "",
    "RPGUID": "",
    "EndPoint": "PayForm/PF.aspx",
    "EINDEX": "300",
    "Amounts": {
      "Amount": 25,
      "Surcharge": 0,
      "TotalAmt": 25
    },
    "Payer": {
      "Firstname": "",
      "Lastname": "",
      "BillingAddress": {
        "StreetAddress": "",
        "City": "",
        "State": "",
        "ZIP": "",
        "Country": ""
      },
      "Email": "",
      "Phone": ""
    },
    "WidOptions": {
      "eVisible": "6E7F",
      "eReadOnly": "0040",
      "eStyles": "0001",
      "eSubmission": "0201",
      "eColors": "#ffffff,#6cca44,#59ff00,#212121,#ffffff,#212121,#ffffff"
    }
  }
}

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.

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 Redirect with query string section of our full PayForm guide.

PayForm manual consent

To use the PayForm to save a card on file, follow the steps in PayForm manual card sale, 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.

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.

Virtual Terminal manual consent

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.

Mobile manual card sale

The relevant methods are described in 1. Charge credit card section of the Android SDK guide and 1. Charge credit card section of the iOS SDK guide.

Mobile manual consent annual

The relevant methods are described in 3. Create annual consent section of the Android SDK guide and 3. Create annual consent section of the iOS SDK 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.

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 Authentication 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 Process a Card Sale.

Manual consent

You can use the following API operations:

• For the REST API, use Create Annual Consent for annual consent and Create Recurring Consent for recurring consent.