GlobePay e-wallet

Interaction diagram

Payment processing through the GlobePay payment method requires merchant's web service, one of the interfaces and the payment platform of Monetix, as well as GlobePay technical facilities.

Operations support

	Interfaces			Amounts in any of supported currencies
	Payment Page	Gate	Dashboard	minimum	maximum
Purchases				1.00
Payouts

You can check the payment amount limits in your project by using Dashboard. To check your payment amount limits, go to Dashboard, select the Projects section and click the Payment methods tab.

Processing scenarios

In the GlobePay method, to perform a purchase operation, you need to redirect a customer to the GlobePay service, while a payout is performed with the notification of a customer through the web service.

The sections that follow provide detailed information about what you need to perform payments and how you can analyze the information on payments and operations.

General information

In the GlobePay method, to perform a purchase by using Payment Page, the merchant web service should send a request with all the required parameters and signature to the Monetix URL and get the callback with the payment result from the payment platform. When opening Payment Page, you can have Payment Page opened with the GlobePay method selected. For more information about preselecting payment methods, see in Preselecting payment methods.

The full sequence and particularities of the purchase process are provided below.

The sections that follow discuss in more details the request format and the Payment Page parameters to use in the GlobePay payment method and provide the information on the format of callbacks with payment results. For the general information on how to use the API, see Payment Page API Description.

Request format

There are several things you need to consider when using the GlobePay method:

1. You must provide values for the basic minimum of parameters. Listed below are the parameters that are required for any payment method:
   • customer_id—unique ID of the customer within your project
   • customer_first_name—customer first name
   • customer_last_name—customer last name
   • customer_email—customer email address
   • project_id—the project ID obtained from Monetix
   • payment_id—payment ID unique within the project
   • payment_currency—payment currency in ISO-4217 alpha-3 format
   • payment_amount—payment amount in minor currency units without any decimal point or comma except for cases where the currency does not have any minor currency units. If the currency has no minor units (that is, the number of digits for minor currency units is zero), then you must set this parameter to the amount in the major currency units. For the information on whether the currency has any minor units, see Currency codes.
2. The currency of payment can be EUR, GBP or USD.
3. To preselect GlobePay as the payment method on Payment Page for customers, pass the code globepay in the force_payment_method parameter in the request for opening.
4. If required, you can also add any other additional parameters Payment Page supports. For information about all parameters available in the GlobePay method, see Payment Page invocation parameters.
5. After you specify all the parameters you need, you must create the signature for the request. For instructions on how to sign a payment request, see Signature generation and verification.

Here is an example of data from a request for Payment Page opening:

EPayWidget.run(
    { 
        payment_id: 'X03936', 
        payment_amount: 10000, 
        payment_currency: 'USD', 
        customer_id: '123',
        customer_first_name: 'John',
        customer_last_name: 'Doe',
        customer_email: 'example@email.com',
        project_id: 0, 
        signature: "kUi2x9dKHAVNU0FYldJrxh4yo+529vySO\/RLCvhtT4DqtVUkDJrOcZzUCwX6R\/ekpZhkIQg=="
    }
)

For information about all parameters available in the GlobePay method, see Payment Page invocation parameters.

Callback format

The GlobePay method uses the standard format for callbacks to deliver purchase results. For more information, see Callbacks in Payment Page.

The following is the example of a callback with an information about successful 100,00 USD purchase from the customer e-wallet testing@globepayinc.com made in the 580 project.

{
        "project_id": 580,
        "payment": {
            "id": "TEST_1554293313510",
            "type": "purchase",
            "status": "success",
            "date": "2019-04-03T12:20:16+0000",
            "method": "GlobePay",
            "sum": {
                "amount": 10000,
                "currency": "USD"
            },
            "description": "TEST_1554293313510"
        },
        "account": {
            "number": "testing@globepayinc.com"
        },
        "customer": {
            "id": "155622456523"
        },
        "operation": {
            "id": 31036000000993,
            "type": "sale",
            "status": "success",
            "date": "2019-04-03T12:20:16+0000",
            "created_date": "2019-04-03T12:18:40+0000",
            "request_id": "ff650d304f361b234",
            "sum_initial": {
                "amount": 10000,
                "currency": "USD"
            },
            "sum_converted": {
                "amount": 10000,
                "currency": "USD"
            },
            "provider": {
                "id": 1216,
                "payment_id": "gq2Z",
                "date": "2019-04-03T12:20:12+0000",
                "auth_code": ""
            },
            "code": "0",
            "message": "Success"
        },
        "signature": "pZr95f+rAb1cm1CW5usL9Ocz/pNyYH6kA3sXwBWwx++iJkwHWAbQAxSfiZi9jA=="
    }
}

The following is the example of a callback for a purchase declined.

{
        "project_id": 580,
        "payment": {
            "id": "ECT_TEST_15548005973333",
            "type": "purchase",
            "status": "decline",
            "date": "2019-04-09T10:31:34+0000",
            "method": "GlobePay",
            "sum": {
                "amount": 10000,
                "currency": "USD"
            },
            "description": ""
        },
        "customer": {
            "id": "15562245652344"
        },
        "operation": {
            "id": 33577000001150,
            "type": "sale",
            "status": "decline",
            "date": "2019-04-09T10:31:34+0000",
            "created_date": "2019-04-09T09:31:34+0000",
            "request_id": "d1b8413f8a9927c458",
            "sum_initial": {
                "amount": 10000,
                "currency": "USD"
            },
            "sum_converted": {
                "amount": 10000,
                "currency": "USD"
            },
            "provider": {
                "id": 1216,
                "payment_id": "",
                "auth_code": ""
            },
            "code": "20000",
            "message": "General decline"
        },
        "signature": "mXgF40MMwqLr6mwHrXwwy7umbCaOTqg3LL0YU2lRo13MXSlk9cPLA4CbuVMCnAsq7Yrw=="
    }
}

Related topics

The following topics might be useful when implementing payments through Payment Page:

• Integration procedure
• Signature generation and verification
• Payment types, operations and payments
• Operation statuses and response codes

General information

In the GlobePay methods, when processing a purchase by using Gate, the merchant web service is required to do the following:

1. Send a request with all the required parameters and signature to the Monetix URL.
2. Perform the redirection of a customer to the GlobePay service.
3. Get the callback with the payment result from the payment platform.

The full sequence and particularities of the purchase processes are provided below.

The sections that follow discuss in more details the request format and the Gate parameters to use in the GlobePay payment method and provide the information about formats of the data for redirecting customers and the information about the format of callbacks with payment results. The general information about working with API see in the API Description section.

Request format

1. You perform purchase by sending the /v2/payment/wallet/globepay/sale request by using POST (HTTP) method. This request refers to the payments by using e-wallets request group: /v2/payment/wallet/{payment_method}/sale.
2. The following objects and parameters must be specified in the request:
   • general—object with general request identification information:
     • project_id—the project ID you obtained from Monetix
     • payment_id—payment ID unique within the project
     • signature—signature created after you specify all the required parameters. For more information about signature generation, see Signature generation and verification
   • customer—object with customer information:
     • id—the unique ID of the customer within your project
     • ip_address—customer device IP
     • first_name—customer first name
     • last_name—customer last name
     • email—customer email address
   • payment—object with purchase information:
     • amount—purchase amount in minor currency units without any decimal point or comma except for cases where the currency does not have any minor currency units. If the currency has no minor units (that is, the number of digits for minor currency units is zero), then you must set this parameter to the amount in the major currency units. For the information on whether the currency has any minor units, see Currency codes.
     • currency—code of purchase currency in the ISO-4217 alpha-3 format
   • • return_url—object with the information where to redirect the customer to when the payment is completed or prematurely terminated by the customer:
       • success—the URL to redirect the customer to after the payment is successfully completed
       • decline—the URL to redirect the customer to after the payment is declined
       • return—the URL to redirect the customer to when they prematurely terminate the payment.
3. The currency of payment can be EUR, GBP or USD.
4. If required, you can also add any other additional parameters Gate supports.

Here is an example of data from a purchase request in the GlobePay method.

{
    "general": {
        "project_id": 255,
        "payment_id": "TEST_15392667771145",
        "signature": "Uhka8CiYAlDlc2wRq60vlSmTTCb0Zp0KrMr5cAVZNLP64Pn2ja9u0filH8Z03Gr0wh8Q=="
    },
    "customer": {
        "id": "123",
        "ip_address": "185.123.193.224",
        "first_name": "John",
        "last_name": "Doe",
        "email": "example@email.com"
    },
    "payment": {
        "amount": 10000,
        "currency": "USD"
    },
    "return_url": {
      "return": "http://example.com/return",
      "success": "http://example.com/success",
      "decline": "http://example.com/decline"
    }
}

Format of customer redirection data

After receiving and processing your purchase request, the payment platform sends a callback to your web service containing the data to redirect the customer to the GlobePay service.

To redirect the customer, use the values of the following parameters in the redirect_data object:

• url—the URL to redirect the customer to
• body—the data to be sent in the request body
• method—the HTTP method to get an HTML page of the website (for example, POST or GET)
• encrypted—this is the service parameter. Ignore the data it contains.

Here is an example of a piece of callback containing the data to redirect the customer.

"redirect_data": {
    "method": "POST",
    "body": {
        "example_parameter_1": "value_1",
        "example_parameter_2": "value_2"
    },
    "encrypted": [],
    "url": "https://example.com/redirect"
}

Callback format

The standard format for callbacks is used to deliver purchase results from GlobePay. For more information, see Callbacks in Gate.

Related topics

The following topics might be useful when implementing payments through Gate:

• Integration procedure
• Signature generation and verification
• Payment types, operations and payments
• Operation statuses and response codes

General information

To perform a payout through the GlobePay method, merchant's web service sends a request with all the required parameters and signature to Monetix URL, and receives a callback with the payment result. The full sequence of the payout process is provided below.

The sections that follow discuss in more details the request format and the Gate parameters to use in the GlobePay payment method and provide the information on the format of callbacks with payout results. The general information about working with API see in the API Description section.

Request format

1. You perform payout by sending the request to the /v2/payment/wallet/globepay/payout endpoint request by using POST (HTTP) method. This request refers to the payments by using e-wallets request group: /v2/payment/wallet/{payment_method}/payout.
2. The following objects and parameters must be specified in any request:
   • general—object with general request identification information:
     • project_id—the project ID you obtained from Monetix
     • payment_id—payment ID unique within the project
     • signature—signature created after you specify all the required parameters. For more information about signature generation, see Signature generation and verification
   • customer—object with customer information:
     • id—the unique ID of the customer within your project
     • ip_address—customer device IP
     • first_name—customer first name
     • last_name—customer last name
     • email—customer email address
   • account—object with customer account information:
     • number—customer account number
   • payment—object with payout information:
     • amount—payout amount in minor currency units without any decimal point or comma except for cases where the currency does not have any minor currency units. If the currency has no minor units (that is, the number of digits for minor currency units is zero), then you must set this parameter to the amount in the major currency units. For the information on whether the currency has any minor units, see Currency codes.
     • currency—code of payout currency in the ISO-4217 alpha-3 format
3. The currency of payment can be EUR, GBP, INR or USD.
4. If required, you can also add any other additional parameters Gate supports.

Here is an example of data from a payout request in the GlobePay method.

{
    "general": {
        "project_id": 199,
        "payment_id": "Payment_2",
        "signature": "2tlMuYxLW9Yu6RETr8pdrQgJguu0BQjXWH6naCA9Ts6o4EVPjLyfbOQ+9ajAteg5lPk96Q=="
  },
    "customer": {
        "id": "customer123",
        "ip_address": "198.51.100.47",
        "first_name": "John",
        "last_name": "Doe",
        "email": "example@email.com" 
  },
    "account": {
        "number": "testing@globepayinc.com"
  },
    "payment": {
        "amount": 10000,
        "currency": "USD"
  }
}

Callback format

The GlobePay method uses the standard format for callbacks to deliver payout results. For more information, see Callbacks in Gate.

The following is the example of a callback with an information about successful 100,00 USD payout made to the customer123 customer ID in the 199 project.

{
        "project_id": 580,
        "payment": {
            "id": "test_0008",
            "type": "payout",
            "status": "success",
            "date": "2019-04-09T10:00:36+0000",
            "method": "GlobePay",
            "sum": {
                "amount": 10000,
                "currency": "USD"
            },
            "description": ""
        },
        "account": {
            "number": "info@canvas-pay.com"
        },
        "customer": {
            "id": "customer123"
        },
        "operation": {
            "id": 35748000001152,
            "type": "payout",
            "status": "success",
            "date": "2019-04-09T10:00:36+0000",
            "created_date": "2019-04-09T10:00:25+0000",
            "request_id": "99cf0cca787c79f9d",
            "sum_initial": {
                "amount": 10000,
                "currency": "USD"
            },
            "sum_converted": {
                "amount": 10000,
                "currency": "USD"
            },
            "provider": {
                "id": 1216,
                "payment_id": "gq2Zo5acppGu",
                "date": "2019-04-09T10:00:26+0000",
                "auth_code": ""
            },
            "code": "0",
            "message": "Success"
        },
        "signature": "pN9TQOzYZwmo+d44P1mQOzUpRJ1R3LmWkN6Xmg+jk+Oi9V9n0cJm8gMGB2vCHABuvoSQ=="
    }
}

The following is the example of a callback for a payout rejected due to insufficient funds on merchant balance.

{
        "project_id": 580,
        "payment": {
            "id": "test_0008",
            "type": "payout",
            "status": "decline",
            "date": "2019-04-09T10:00:36+0000",
            "method": "GlobePay",
            "sum": {
                "amount": 10000,
                "currency": "USD"
            },
            "description": ""
        },
        "account": {
            "number": "info@canvas-pay.com"
        },
        "customer": {
            "id": "customer123"
        },
        "operation": {
            "id": 35748000001152,
            "type": "payout",
            "status": "decline",
            "date": "2019-04-09T10:00:36+0000",
            "created_date": "2019-04-09T10:00:25+0000",
            "request_id": "99cf0cca787c79f9d",
            "sum_initial": {
                "amount": 10000,
                "currency": "USD"
            },
            "sum_converted": {
                "amount": 10000,
                "currency": "USD"
            },
            "provider": {
                "id": 1216,
                "payment_id": "gq2Zo5acppGu",
                "date": "2019-04-09T10:00:26+0000",
                "auth_code": ""
            },
            "code": "3028",
            "message": "Insufficient funds on merchant balance"
        },
        "signature": "pN9TQOzYZwmo+d44P1mQOzUpRJ1R3LmWkN6Xmg+jk+Oi9V9nrtJm8gMGB2vCHABuvoSQ=="
    }
}

Related topics

The following topics might be useful when implementing payments through Gate:

• Integration procedure
• Signature generation and verification
• Payment types, operations and payments
• Operation statuses and response codes

• single payout—you specify the currency and amount for a payout available for this method and fill in all the fields required for the selected payment method on the Dashboard pages.
• as a part of a mass payment—all the parameters are specified in a CSV file. Refer to the Payouts by using Gate section for the parameters required by your payment method.

Information about completed payouts is available for viewing in the Payments and Manual Payments sections of Dashboard.

For more information about payout processing by using Dashboard, see Performing payouts.

General information

For the GlobePay method the testing of purchases by using Payment Page and Gate, payouts by using Gate.

Testing can be performed within a test project, to enable and disable the testing availability, contact Monetix technical support via support@monetix.pro.

When performing a test payment, take into account that you must specify the identifier of the test project in the requests, available currencies for testing purchases are EUR, GBP, USD, for testing payouts—EUR, GBP, INR, USD. The interfaces of the payment forms emulator of Payment Page and GlobePay differ from the production environment.

Test payments statuses

When testing purchases, the final payment status is determined by the amount specified in the request:

• decline status with 40000 or 40400 amount
• success status with any other amount

When testing payouts, the final payment status is determined by the amount specified in the request:

• decline status with 40000 or 40400 amount
• success status with any other amount

Testing purchase by using Payment Page

To perform a test purchase by using Payment Page, do the following:

1. Send a correct test request for Payment Page opening to the payment platform.
2. If the globepay method was not specified in the request—select the method on the emulator page.
3. Click the Continue payment button.
4. Click the Success or Decline button (depending on the amount specified in the request).
5. Accept a callback with information about the payment result.

The full information about purchase process by using GlobePay through Payment Page is provided in the section Purchase by using Payment Page.

Testing purchase by using Gate

To perform a test purchase by using Gate, do the following:

1. Send a correct test request for purchase to the payment platform.
2. Accept a callback with redirection data.
3. Go to the received URL and click the Success or Decline button (depending on the amount specified in the request).
4. Accept a callback with information about the payment result.

The full information about purchase process by using GlobePay through Gate is provided in the section Purchase by using Gate.

Testing payout by using Gate

To perform a test payout by using Gate, send a correct test request to the payment platform and accept a callback with information about the payment result. The full information about payout process by using GlobePay through Gate is provided in the section Payout by using Gate.

As with other payment methods Monetix offers, when using this method, you have several options to analyze the information about payments and operations.

You can load and analyze all the necessary information in Dashboard (dash-light.trxhost.com), for instance you can use the analytic panels in the Analytics section for this purpose.

Also, you can export the information for further analysis by using third party analytical tools. The following options are available:

• Dashboard allows you to download reports in CSV format by using the tools in the Reports section. You can perform export as a one-time or regular download of data to your local computer.
• Data API allows you to have payment information exported in JSON format and delivered to a URL you specify. The payment information is exported by means of sending requests to the /operations/get endpoint.

If you have any further questions regarding payment data analysis, contact Monetix technical support.