Payments with payment cards

For payment card processing Payment Page supports the following operations:

The list of supported payment card types is specified in Supported payment cards.

In order to comply with the recommendations of VISA and Mastercard, customers are allowed to initiate payments on expired cards. To enable this feature, contact the ECommPay technical support. If the functionality is enabled, when the customers enters an expired card on the payment page, a warning is displayed to reduce the number of input errors and allow the customers to change the entered data.

In accordance with the recommendations of the Visa and Mastercard for 2020, the payment platform supports the possibility of making payments on expired cards. If the functionality is enabled, a corresponding warning is displayed when the customer enters expired card details in the payment form, and the payment is made in accordance with the Issuer's decision. To enable this feature, contact the ECommPay technical support.

Payment processing

Payment processing

Payment Page supports payments with holding funds and direct withdrawal of funds from payment cards. The payment type is defined by the card_operation_type parameter or by the project settings when the parameter is not sent.

Payments with direct withdrawal performed by default. To change the settings, contact technical support by email support@ecommpay.com.

For the full list of the supported parameters see Payment Page invocation parameters.

Payment with direct withdrawal of funds

A direct withdrawal payment means authorization with instant confirmation of debiting funds from a payment card.

To perform a payment with direct withdrawal of funds from payment cards, send sale in the card_operation_type parameter.

Also this type of operation is used in case of AFT payment. AFT (Card2Account) payments are used to repay loans in MFIs by using payment cards. For more information or to enable and configure the service, refer to your Key Account Manager.

Payment with holding funds on a payment card

When making payments from a payment card, you can hold funds temporarily on the customer's card. You will be assured that funds are available and in holding.

To perform a payment with holding funds on payment cards, send auth in the parameter to pass to Payment Page card_operation_type.

Once you have received a confirmation of the holding funds, when you are ready to confirm the payment, you send a request for withdrawal of the funds to Gate. You can confirm the withdrawal of the full payment by the request /v2/payment/card/capture. Alternatively you can cancel the hold on the entire payment by the request /v2/payment/card/cancel. Also automatic confirmation or cancellation of funds withdrawal can be set up for your project when the request is not send within the specified time period.

For more information, see One-time purchase processing.

COF payments processing

Payment Page supports performing payments by using the saved data of a customer payment instrument: card, account, e-wallet, mobile number, etc.

Credential-on-File payment is a payment under which a cardholder grants the permission to a merchant, payment facilitator, staged e-wallet operator or payment facilitator’s sub-merchant to store data that is associated with the payment card or payment method, which includes, but not limited to payment card number, expiry date, payment token, and authorizes the merchant to withdraw funds from the payment card using the stored credentials.

Types of COF payments

There are several types of COF payments:

  • Payments on stored credentials with holding funds and with the direct withdrawal of funds through Gate when a cardholder enters the CVV to confirm the payment. For more information, see Saving customer payment data.
  • OneClick—initiated by a cardholder unscheduled withdrawal of funds from a payment card in one click without predetermined payment amount.
  • Regular payments—initiated on your side withdrawal of funds from a payment card that are processed at fixed intervals and with fixed amount on the basis of the predetermined with the cardholder terms. For example, a weekly online newsletter subscription or the monthly replenishment of mobile phone balance.
  • Autopayment—initiated on your side unscheduled withdrawal of funds from a payment card upon the occurrence of certain conditions that are predetermined with the cardholder and without fixed amount. For example, the payment of an administrative fine or the outstanding mobile phone balance.
  • Payments by using tokens of payment cards. For more information on tokens, see Payments by using tokens.

Registration of COF payments

When a customer agrees to subscribe on performing OneClick, Regular payments or Autopayments, pass the necessary parameters for COF payment registration in the recurring parameter in the request for payment.

The data is passed in Payment Page in a JSON object. This object is one string encoded in URL-encoded. The encoded string is passed in Payment Page in the recurring parameter of the request for payment. The structure of the JSON object is given in the recurringinfo model.

Figure: Request for COF payment registration

Source JSON object:

recurring={"register":true,"type":"R","expiry_year":2020,"expiry_month":"01","period":"D","time":"10:00:00","start_date":"15-11-2018","scheduled_payment_id":"A2323"}

Example of URL to open Payment Page with the passed recurring parameter:

https://paymentpage.ecommpay.com/payment?payment_id=ECT_TEST_1534240436687&payment_currency=USD&language_code=en&mode=purchase&project_id=11&payment_amount=15000&customer_id=5&force_payment_method=card&css_modal_wrap=standart&payment_id=EP1f69-9b2e&recurring=%7B%22register%22%3Atrue%2C%22type%22%3A%22C%22%2C%22expiry_year%22%3A2025%2C%22expiry_month%22%3A%2201%22%2C%22period%22%3A%22DR%22%2C%22time%22%3A%2210%3A00%3A00%22%7D&signature=uTN7fx9tQUtHCH%2FPV899%2FyQ9xP5scMI8ju4ah2xj%2BpkRrSk5Itt4OqXpLSKmn%2BhSRKHIhU7QE39kdDbrr1SUkg%3D%3D

For the complete list of parameters supported by Payment Page, see Payment Page invocation parameters.

Parameters in the recurring parameter of JSON object

In this section the valid values of the parameters that are included in the recurringinfo object are listed.

Table 1. Parameters of the recurring JSON object
Parameter Mandatory Format Description Example
register No boolean A parameter that indicates a COF payment registration true
type No string COF payment type. The available values:
  • R — Regular payment
  • U — Autopayment
  • COneClick
R
amount No integer The amount of the subsequent COF payments 1000
expiry_day No integer The day of the COF payment expiry date 25
expiry_month No integer The month of the COF payment expiry date 11
expiry_year No integer The year of the COF payment expiry date 2020
interval No integer The interval of Regular payments performing from 1 to 100, for example, each three weeks or each two days. The parameter is necessarily used in conjunction with period 3
period No string The period of Regular payments performing. The available values:
  • D — daily
  • W — weekly
  • M — monthly *
  • Q — quarterly
  • Y — annually

* if the set day is not available in the next month, for example, 31, the payment is performed on the last day of the month.

D
time No string The time of Regular payments performing in the hh:mm:ss (UTC0) format 10:00:00
start_date No string The start date of Regular payments performing in the dd-mm-yyyy format. The parameter is necessarily used in conjunction with scheduled_payment_id 15-11-2020
scheduled_payment_id No string The ID of the Regular payment in your system. The parameter is necessarily used in conjunction with start_date. A2323

Regular payment registration

You can register a Regular payment in any of the following ways:
  • If you store the payment schedule on your side, pass the parameters register=true and type=R in the object recurring in the request for payment by using Payment Page. To activate and perform payments on the schedule, send a request to Gate.
  • In addition to the above described parameters, pass the period and time of Regular payments performing, in this case the payment schedule is saved on Gate side. To activate and perform payments on the schedule, send a request to Gate.
  • In addition to the above described parameters, pass the start date of a payment performing in the start_date parameter and the unique ID of the payment in your system in the scheduled_payment_id. In this case the payment schedule is saved on Gate side and the performing of the Regular payments is activated automatically.
If you try to register another type of COF payment and pass one of these parameters, they are ignored. For more information, see Credential-on-file (COF) purchases.

Activation of a COF payment

After registering a COF payment you activate the automatic fund withdrawals by sending a request to Gate. For more information, see Credential-on-file (COF) purchases.

While the COF payment is active you do not need to send the request for fund withdrawals, they are performed automatically according to the specified terms.

Updating of the terms of a COF payment

At any time you can update or change the terms of payment a payment on stored credentials by sending a request to Gate. For example, you can change the period or the performing time of a withdrawal. For more information, see Credential-on-file (COF) purchases.

Cancellation of a COF payment

You can cancel the performing of a payment on stored credentials before its expiration date by sending a request to Gate. For more information, see Credential-on-file (COF) purchases.

Cancellation of COF payments by customer

If a customer decides to cancel the COF payment subscription, he contacts the issuer of the payment card to close the card account or cancel all subscriptions connected to the card. After cancellation, an attempt to perform a COF payment by using the card is declined with a corresponding error code and message, which you receive in the Callback after the payment processing. As well as the card is removed from the list of saved instruments in Payment Page.

MO/TO Payment Processing

Mail Order/Telephone Order (MO/TO) payment is a CNP (card-not-present) payment when a cardholder provides you with bank card credentials via mail or telephone to perform a payment. MO/TO payments are processed by using Payment Page and Gate.

MO/TO payment processing by using Payment Page

MO/TO payments are different from the usual ones. MO/TO payment is a type of CNP payments, when a bank card and a cardholder are not physically present. The bank card credentials are provided by its holder by mail, telephone, facsimile or other communication to create an invoice and are entered in a payment page by your operator.

To perform a MO/TO payment by using Gate, pass one of the necessary values of the moto_type parameter in the payment object:
  • 1 for the Mail Order (MO) payment
  • 2 for the Telephone Order (TO) payment

For the complete list of parameters supported by Payment Page, see Payment Page invocation parameters.

Figure: Example of the request for performing a MO/TO payment by using Payment Page in the Purchase mode

EPayWidget.run(
    { payment_id: 'X03936', 
      payment_amount: 1000, 
      payment_currency: 'EUR', 
      project_id: 13, 
      customer_id: 'user123', 
      moto_type: 2,
      signature: "kUi2x9dKHAVNU0FYldJrxh4yo+52Kt8KU+Y1Y4HASCQ9vySO\/RLCvhtT4DqtVUkDJrOcZzUCwX6R\/ekpZhkIQg=="
    }
)

Passing the cvv parameter

If moto_type=1 for Mastercard and Visa bank cards the cvv parameter in the object card becomes optional. For other card types parameter is mandatory.

If moto_type=2 for Mastercard bank cards the cvv parameter in the object card becomes optional. For other card types parameter is mandatory.

MO/TO payment processing by using Gate

For more information on MO/TO payment processing by using Gate, see MO/TO Payment Processing.

Supported payment cards

Payment Page supports processing payment and pre-selecting the payment method type with the following payment card types:

Card type Code
American Express amex
Belcard belcard
Maestro maestro
Mastercard mastercard
Troy troy
Mir mir
VISA visa