Download the PHP package verifone/core without Composer

Verifone BlueCommerce Payment Gateway Implementation

This repository contains implementation for Verifone BlueCommerce Payment Gateway used in Nordics. Not compatible with the Verifone Global eCommerce Gateway (https://verifone.cloud/)

Table of Contents

• 1. Installation
• 2. Basic information
  • 2.1 Contact
  • 2.2 Configuration - Development mode
  • 2.3 Configuration - Production mode
  • 2.4 Delayed URL
• 3. Usage
  • 3.1 Fetch available payment methods
  • 3.1.1 Code example:
  • 3.2 Generate RSA keys
  • 3.2.1 Code example
  • 3.3 Make payment request
  • 3.3.1 Code example
  • 3.4 Parse payment response
  • 3.4.1 Code example
  • 3.5 Check payment status
  • 3.5.1 Code example
  • 3.6 Make refund request
  • 3.6.1 Code example
  • 3.7 Credit Cards
  • 3.7.1 Add a new card - code example
  • 3.7.2 Fetch available payment cards - code example
  • 3.7.3 Remove payment card - code example
• 4 Notes
  • 4.1 Payment Methods
  • 4.2 Currency
  • 4.3 Language
  • 4.4 Country

1. Installation

2. Basic information

2.1 Contact

If you want to contact support or customer service, please send an email to: [email protected]

2.2 Configuration - Development mode

Library provides functionality for development mode.

For development mode, you have to use a configuration like the below:

Library provides test keys:

• private key for the shop available in the Verifone/Core/Tests/Integration/Assets/demo-merchant-agreement-private.pem
• public key for the payment service available in the Verifone/Core/Tests/Integration/Assets/point-e-commerce-test-public-key.pem

If you want to use development mode, you have to contact the customer service because our IT department must add the IP to the allowed list

2.3 Configuration - Production mode

For production mode, you have to add a possibility to generate a new key pair and provide the public key into the payment service. Code example for generating a new pair is available here: 3.2 Generate RSA keys

Verifone public key could be found from TCS Client portal by the merchant.

For production mode, you have to use a configuration like in the example below:

Merchant id could be found from TCS Client by the merchant.

2.4 Delayed URL / S2S Callback

Verifone Service sends a request on the URL with information about the transaction. When the response code is different from 200, Verifone Service will repeat the request 24h since the original request.

Merchant has to provide that delayed URL into Verifone’s TCS Client, so must have a possibility to get that URL from the module.

3. Usage

That library has integration and unit tests. If you want, you could find more information about implementation examples there.

3.1 Fetch available payment methods

Each merchant has its own payment methods. To fetch all available payment methods, you have to use GetAvailablePaymentMethodsService.

After fetch payment methods, you should store them in the system.

3.1.1 Code example:

All available payment methods in the notes section: Payment Methods

3.2 Generate RSA keys

To enable live (production) mode, the merchant must provide the shop public key to the Verifone customer service. Public and private keys are using in each request/response action with the Verifone service.

Library provides functionality for generating new key pairs.

3.2.1 Code example

3.3 Make payment request

3.3.1 Code example

Now you could attach $form on the HTML page, and it automatically will redirect customers into payment service.

If you want to get data as a json (array) you could use that code for create $container

3.4 Parse payment response

Verifone has functionality for resending the payment confirmation. But, for that, you have to create a controller that will handle the same response as the regular one.

3.4.1 Code example

3.5 Check payment status

Sometimes payment verification could take more time for many reasons.

For example, customers could close the browser tab before returning to the shop or verify if the order is refunded (partially or total).

For that (and similar) cases, you could create (for example) a cron task that fetches all transactions for the order or a controller action.

Cron functionality is not required when you create delayed success action. Verifone Service sends a request on the URL with information about the transaction. When the response code is different from 200, Verifone Service will repeat the request 24h since the original request.

3.5.1 Code example

3.6 Make refund request

3.6.1 Code example

4516533313 is the transaction number from the payment response. See $transactionId in 3.4.1

3.7 Credit Cards

3.7.1 Add a new card - code example

Now you could attach $form on the HTML page, and it automatically will redirect customers into payment service.

If you want to get data as a JSON (array), you could use that code to create $container.

If you need to add Recurring Card, you could implement it like that:

3.7.2 Fetch available payment cards - code example

3.7.3 Remove payment card - code example

4 Notes

4.1 Payment Methods

4.2 Currency

The system uses currency code in the ISO 4217 standard. More information: https://en.wikipedia.org/wiki/ISO_4217

Examples:

• EUR - 978
• SEK - 752

4.3 Language

Available languages in the payment service:

• fi_FI
• sv_SE
• no_NO
• dk_DK
• sv_FI
• en_GB

If you use code, which is not available, then en_GB will be used as a default.

4.4 Country

The system uses country codes in the numeric ISO 3166-1 standard. More information: https://en.wikipedia.org/wiki/ISO_3166-1_numeric