QR Ph

Introduction

QR Ph is a payment method which allows you to process payments in Philippine pesos by using bank accounts and e-wallets in the Philippines. This method supports purchases.

This article provides information about working with the QR Ph method: general insights are presented in the Overview section, while information about the actions required to process payments and perform other actions is presented in the sections that follow.

General information

Interaction diagram

Payment processing by using the QR Ph method involves the merchant's web service, one of ecommpay interfaces, the ecommpay payment platform, and technical facilities of the provider service.

Operations support

Various platform interfaces can be used to process payments and perform operations using the QR Ph method. Purchases can be processed by using Payment Page, Gate and Dashboard (using payment links). At the same time, regardless of the interfaces used, the amount of a single purchase can be 100.00 PHP minimum and 50,000.00 PHP maximum. For more information about limitations on purchase amounts, refer to your ecommpay account manager.

In case of using the QR Ph method, the amount of a single purchase can be 100.00 PHP minimum and 50,000.00 PHP maximum. For more information about limitations on purchase amounts, refer to your ecommpay account manager.

Processing scenarios

To perform a purchase by using the QR Ph method, the customer needs to scan a QR code via a mobile application.

The customer payment scenario via Payment Page (in the basic case where the customer chooses the method and is redirected from the final page of the payment form to the web service) looks like this.

General scenarios of processing purchases can be presented as follows.

Scenarios for performing operations via the main interfaces of the payment platform correspond to those presented in the diagrams. Similarly, when additional features (such as payment links) are used, scenarios for performing operations also correspond to the specifics of those features.

General information

To process a purchase through Payment Page by using the QR Ph method, the merchant's web service is required to send a request with all required parameters and signature to the ecommpay URL and receive a callback with the result. The full sequence and special aspects of purchase processing are provided below.

Information about the formats of requests and callbacks used for processing payments by using the QR Ph method via Payment Page is presented further in this section; general information about working with the Payment Page API is presented in Interaction concepts.

Request format

There are several things you need to consider when sending purchase requests by using the QR Ph method:

1. The following parameters required for any payment must be specified:
   • project_id—project identifier obtained from ecommpay during integration
   • payment_id—payment identifier unique within the project
   • payment_currency—payment currency code in the ISO-4217 alpha-3 format
   • payment_amount—payment amount in the smallest currency unit
   • customer_id—customer identifier unique within the project

   Depending on the payment processing provider, other parameters may be required in the purchase requests (such as customer_first_name, customer_last_name, and customer_email). For more information about potentially required parameters, contact your ecommpay account manager.

2. The following parameters required for any payment must be specified: project_id, payment_id, payment_currency, payment_amount, customer_id.

   Depending on the payment processing provider, other parameters may be required in the purchase requests.

3. If you need to have the payment form displayed with the QR Ph method selected, set the force_payment_method parameter to ph-qr.
4. Additionally, any other parameters available for working with Payment Page can be used (details).
5. After all target parameters are specified, generate a signature (details).

Thus, a correct request for opening the payment form using the QR Ph method must contain the project identifier, basic payment information (identifier, amount, and currency code), customer identifier and signature.

{
   "project_id": 120,
   "payment_id": "580",
   "payment_amount": 1000000,
   "payment_currency": "PHP",
   "customer_id": "customer1",
   "signature": "kUi2x9dKHAVNU0FYldOcZzUCwX6R\/ekpZhkIQg=="
}

{
   "project_id": 120,
   "payment_id": "580",
   "payment_amount": 1000000,
   "payment_currency": "PHP",
   "customer_id": "customer1",
   "signature": "kUi2x9dKHAVNU0FYldOcZzUCwX6R\/ekpZhkIQg=="
}

Callback format

The QR Ph method uses the standard format for callbacks to deliver purchase results. For more information, see Callbacks.

The following is the example of a callback with information about a 10,000.00 PHP purchase made by the customer_123 customer in the 1234 project.

{
    "project_id": 1234,
    "payment": {
        "id": "payment_47",
        "type": "purchase",
        "status": "success",
        "date": "2022-03-25T11:08:45+0000",
        "method": "QRPH",
        "sum": {
            "amount": 1000000,
            "currency": "PHP"
        },
        "description": ""
    },
    "customer": {
        "id": "customer_123"
    },
    "operation": {
        "id": 28,
        "type": "sale",
        "status": "success",
        "date": "2022-03-25T11:08:45+0000",
        "created_date": "2022-03-25T11:08:05+0000",
        "request_id": "9e32835fb27907e0b08569d7d336c5117242b5cf60a4e17839",
        "sum_initial": {
            "amount": 1000000,
            "currency": "PHP"
        },
        "sum_converted": {
            "amount": 1000000,
            "currency": "PHP"
        },
        "code": "0",
        "message": "Success",
        "provider": {
            "id": 00000,
            "payment_id": "123abc123-321",
            "auth_code": ""
        }
    },
    "signature": "U7HQO7ToISZhMPKdM4Xr4DScs9CRd4xeYG2Q=="
}

The following is the example of a callback with information about a declined purchase.

{
    "project_id": 1234,
    "payment": {
        "id": "payment_47",
        "type": "purchase",
        "status": "decline",
        "date": "2022-03-25T11:20:30+0000",
        "method": "QRPH",
        "sum": {
            "amount": 1000000,
            "currency": "PHP"
        },
        "description": ""
    },
    "customer": {
        "id": "customer_123"
    },
    "operation": {
        "id": 31,
        "type": "sale",
        "status": "decline",
        "date": "2022-03-25T11:20:30+0000",
        "created_date": "2022-03-25T11:19:53+0000",
        "request_id": "fff3d5f8d5d31bc460b68b57dc63f4b482e906eb",
        "sum_initial": {
            "amount": 1000000,
            "currency": "PHP"
        },
        "sum_converted": {
            "amount": 1000000,
            "currency": "PHP"
        },
        "code": "20000",
        "message": "General decline",
        "provider": {
            "id": 00000,
            "payment_id": "0cf4215c-8978",
            "auth_code": ""
        }
    },
    "signature": "J7W15rkqrLzTCD4HkoM4qoEnl4z2iFYv58P4VnHANu445/jmY+g=="
}

Useful links

The following articles can be useful when implementing purchases via Payment Page:

• Interaction concepts—about the interaction with the payment platform by using Payment Page.
• Signature generation and verification—about the procedure of generating and verifying signatures in requests and callbacks.
• Payment models and statuses—about the types, processing models, and possible statuses of supported payments and operations.
• One-time one-step purchase—about processing of one-time one-step purchases by using Payment Page.
• Information of operations performing—about error and response codes that are used in the payment platform to record information about performing of operations.

General information

To process a purchase through Gate by using the QR Ph method, the merchant's web service is required to do the following:

1. Send a request with all the required parameters and signature to the ecommpay URL.
2. Receive an intermediate callback from the payment platform and display a QR code and payment instructions to the customer.
3. Receive the final callback from the payment platform.

The full sequence and special aspects of purchase processing are provided below.

Information about the formats of requests and callbacks used for processing payments by using the QR Ph method via Gate is presented further in this section. General information about working with the Gate API is presented in Interaction concepts.

Request format

There are several things you need to consider when sending purchase requests by using the QR Ph method:

1. To initiate each purchase, send a separate POST request to the /v2/payment/qr/ph-qr/sale endpoint.
2. Each request must include the following objects and parameters:
   • Object general—general purchase information:
     • project_id—project identifier obtained from ecommpay during integration
     • payment_id—payment identifier unique within the project
     • signature—request signature generated after all required parameters are specified (details—in the Signature generation and verification) (details)
   • Object payment—payment information:
     • amount—payment amount in the smallest currency unit
     • currency—payment currency code in the ISO-4217 alpha-3 format
   • Object customer—customer information:
     • id—customer identifier unique within the project
     • ip_address—customer IP address relevant for the initiated payment

   Depending on the payment processing provider, other parameters may be required in the purchase requests (such as the parameters for specifying the customer's first and last names and email address). For more information about potentially required parameters, contact your ecommpay account manager.

3. Additionally, any other parameters included in the specification can be used.

Thus, a correct purchase request by using the QR Ph method must contain the project identifier, basic payment information (identifier, amount, and currency code), customer identifier and IP address and the signature.

{
  "general": {
    "project_id": 210,
    "payment_id": "test_payment",
    "signature": "PJkV8ej\/UG0Di8hTng6JvipTv+AWoXW\/9MTO8yJA=="
  },
  "payment": {
    "amount": 1000000,
    "currency": "PHP"
  },
  "customer": {
    "id": "customer123",
    "ip_address": "192.0.2.0"
  }
}

{
  "general": {
    "project_id": 210,
    "payment_id": "test_payment",
    "signature": "PJkV8ej\/UG0Di8hTng6JvipTv+AWoXW\/9MTO8yJA=="
  },
  "payment": {
    "amount": 1000000,
    "currency": "PHP"
  },
  "customer": {
    "id": "customer123",
    "ip_address": "192.0.2.0"
  }
}

Formats of intermediate callbacks for displaying QR codes to customers

Each payment made with the QR Ph method requires displaying QR codes to customers. To display QR codes it is necessary to receive an intermediate callback from the payment platform and use the information included in the display_data array. The format of such callbacks is standard (details), and the following objects and parameters are included in the display_data array:

• type—type of data (the value is always qr_img)
• title—the name of the transferred data that needs to be displayed to the customer (the value is always qr_img)
• data—a string based on which a QR code should be generated on the web service side (according to ISO/IEC 18004:2015)

"display_data": [
            {
                "type": "qr_img",
                "title": "qr_img",
                "data": "data:image\/png;base64,iVB..."
            }
]

Final callback format

The QR Ph method uses the standard format for callbacks to deliver purchase results. For more information, see Callbacks.

The following is the example of a callback with information about a 10,000.00 PHP purchase made by the customer_123 customer in the 1234 project.

{
    "project_id": 1234,
    "payment": {
        "id": "payment_47",
        "type": "purchase",
        "status": "success",
        "date": "2022-03-25T11:08:45+0000",
        "method": "QRPH",
        "sum": {
            "amount": 1000000,
            "currency": "PHP"
        },
        "description": ""
    },
    "customer": {
        "id": "customer_123"
    },
    "operation": {
        "id": 28,
        "type": "sale",
        "status": "success",
        "date": "2022-03-25T11:08:45+0000",
        "created_date": "2022-03-25T11:08:05+0000",
        "request_id": "9e32835fb27907e0b0856e336c5117242b5cf60a4e17839",
        "sum_initial": {
            "amount": 1000000,
            "currency": "PHP"
        },
        "sum_converted": {
            "amount": 1000000,
            "currency": "PHP"
        },
        "code": "0",
        "message": "Success",
        "provider": {
            "id": 00000,
            "payment_id": "123abc123-321",
            "auth_code": ""
        }
    },
    "signature": "U7HQO7ToISZhMPKdM4Xr4DSX2toYzFvoB3cs9CRd4xeYG2Q=="
}

The following is the example of a callback with information about a declined purchase.

{
    "project_id": 1234,
    "payment": {
        "id": "payment_47",
        "type": "purchase",
        "status": "decline",
        "date": "2022-03-25T11:20:30+0000",
        "method": "QRPH",
        "sum": {
            "amount": 1000000,
            "currency": "PHP"
        },
        "description": ""
    },
    "customer": {
        "id": "customer_123"
    },
    "operation": {
        "id": 31,
        "type": "sale",
        "status": "decline",
        "date": "2022-03-25T11:20:30+0000",
        "created_date": "2022-03-25T11:19:53+0000",
        "request_id": "fff3d5f8d5d31bc460b68b57dc63f4b482e906eb",
        "sum_initial": {
            "amount": 1000000,
            "currency": "PHP"
        },
        "sum_converted": {
            "amount": 1000000,
            "currency": "PHP"
        },
        "code": "20000",
        "message": "General decline",
        "provider": {
            "id": 00000,
            "payment_id": "0cf4215c-8978",
            "auth_code": ""
        }
    },
    "signature": "J7W15rkqrLzTCD4HkoM4qom8C4z2iFYv58P4VnHANu445/jmY+g=="
}

Useful links

The following articles can be useful when implementing purchases via Gate:

• Interaction concepts—about the interaction with the payment platform by using Gate.
• Signature generation and verification—about the procedure of generating and verifying signatures in requests and callbacks.
• Payment models and statuses—about the types, processing models, and possible statuses of supported payments and operations.
• One-time one-step purchase—about processing of one-time one-step purchases by using Payment Page.
• Information of operations performing—about error and response codes that are used in the payment platform to record information about performing of operations.