PayMaster

* — to enable your clients to create subscriptions, when configuring integration with this payment method, choose Bank Card and/or WebMoney as the payment method. Subscriptions will not work for other payment methods.

Configuration details on the payment gateway side

Login to the payment gateway and enter the following configuration details:

• Signature type — must match the type selected in BILLmanager
• Secret key — secret word inside your PayMaster account
• Payment notification — https://<BILLmanager URL>/mancgi/pmasresult
• Success redirect — https://<BILLmanager address>/billmgr?func=payment.success
• Failure redirect — https://<BILLmanager address>/billmgr?func=payment.fail
• Payment notification — POST
• Allow URL change — select the check box
• User should return back to web-site — select the check box. Otherwise, payment information won't be sent to BILLmanager
• Resend Payment Notification in case of failure — select the check box

If you intend to use recurrent payments, you need to set up Direct signature.

BILLmanager configuration details

Payment module can be connected in the section Provider → Payment methods .  The connection wizard consists of three steps:

Step 1. Select the payment module "PayMaster".

Step 2. Specify the information required for integration with the payment system.

Step 3. Specify the internal (within BILLmanger) payment method parameters.

Configuring integration

The option Client offers to use the existing account on the payment system side, or create a new account.  If "Use existing" is selected, specify the data for integration in the form:

• Integration settings block:
  • Merchant id — ID of the account under which the Company is registered in PayMaster system.
  • Signature type — type of data signature verification upon receipt of payment receipt notification.
  • Payment method — specify the permitted payment method.
  • Payment gateway URL — specify the gateway through which payment is to be performed.
  • Secret key — secret key in PayMaster system.

• Recurring payments block:
  

  • Recurring payments — enable the use of recurrent payments.
  • Signature type — type of Direct type data signature verification for automatic payments.
  • Successful autopayment return page — the page to which customer is redirected after a successful payment.
  • Failed automatic payment return page — the page to which customer is redirected after a failed payment attempt.
  • Secret key — secret key in PayMaster Direct system.        

Redirecting after payment

This payment method supports the function for redirecting the customer after payment to the corresponding page. You can set the page to which the customer will be redirected after a successful or failed payment or subscription configuration.  To set the page, go to Provider → Payment methods → Edit and specify the URL of the corresponding pages in the fields:

• Successful payment return page;
• Failed payment return page; 
• Successful autopayment return page;
• Failed automatic payment return page;
• Return page if subscription is enabled successfully;
• Return page if subscription activation has failed.

Payment return

Configuration on the payment system side

Log into your PayMaster account. In "Users" create a new user with login method "Automatic access". Users must be assigned the "Operationist" role (viewing payment status and list of payments) or "Accountant" role (Operationist + payment return + list of returns + hold confirmation or cancellation).

Configuration BILLmanager side

In Payment → Method settings, enable Allow payments return , and specify the login and password of the user you have created at the previous step. 

Technical information

PayMaster payment module records its activity in logs:

• pmpaymaster.log — log file of payment module configuration and automatic payments;
• pmaspayment.log — payment log file;
• pmasresult.log — log file of payments verification after IPN message receipt;
• pmasrecurring.log — log file of automatic payment activation;
• pmasrecurringresult.log — log file of response from the payment system at activation of recurrent payments. This log file may not exist of no recurrent payments are activated.