User Manager/User payments

Supported payment methods

At the moment only Authorize.Net payments are supported. PayPal support is in development.

Authorize.Net

Requirements

To allow Authorize.Net payments for users the following requirements must be met:

• User Manager v3.0 package installed on the router, 3.0beta5 available at the moment (See: Getting started);
• User Manager subscriber created (See: Getting started);
• Subscriber must have merchant account in Authorize.Net gateway;
• Web server on the router must be configured to support secure SSL connections (See HTTPS connection enabling);

Setup

HTTPS connection enabling

Creating certificate

Trusted SSL Certificate can be bought from trusted authorities, for example, VeriSign. An unsigned certificate can be generated by hand, for example, using command apache2-ssl-certificate on a Linux box;

Importing certificate

Certificate file can be then uploaded to the router and imported with command

/certificate import file-name=...

The command should return

    certificates-imported: 1
    private-keys-imported: 1
           files-imported: 1
      decryption-failures: 0
 keys-with-no-certificate: 0

If it doesn't, could happen that the file contains private key and certificate sections in incorrect order. In this situation the output should be

    certificates-imported: 1
    private-keys-imported: 0
           files-imported: 1
      decryption-failures: 0
 keys-with-no-certificate: 1

Just repeat the same command

/certificate import file-name=...

once again and the output should be this time

    certificates-imported: 0
    private-keys-imported: 1
           files-imported: 1
      decryption-failures: 0
 keys-with-no-certificate: 0

Now certificate is imported correctly and ready for use;

Enabling WWW SSL

SSL connections for WWW server can be enabled with command

/ip service set www-ssl disabled=no certificate=cert1

where cert1 must be replaced by a correct certificate name (from /certificate section)

Merchant account configuration

Relay URL

Relay URL list must either be empty or contain URL to the User Manager router. For example, if you are using userman.mt.lv as User Manager router, then Relay URL list must contain URL https://userman.mt.lv/ (works with and without trailing slash). Relay URL list can be configured in Authorize.Net merchant gateway under Account > Settings > Response/Receipt URLs

API Login ID

API Login ID is shown in Authorize.Net merchant gateway under Account > Settings > API Login ID and Transaction Key.

Transaction Key

Transaction Key can be obtained in Authorize.Net merchant gateway under Account > Settings > Obtain Transaction Key.

MD5-Hash value

MD5-Hash value can be set in Authorize.Net merchant gateway under Account > Settings > MD5-Hash.

Payment Form

Payment Form configuration can be found in Authorize.Net merchant gateway under Account > Settings > Payment Form. The look of this form is customizable here. While the only required fields for processing transaction are credit card number and expiration date, another fields are allowed to be shown in the form. Form customization is up to merchant.

Subscriber configuration

Subscribers have a set of specific Authorize.Net fields which must be configured properly to allow Authorize.Net payments:

• Only subscribers have Authorize.Net fields, other customers don't;
• Field values can be changed only in customer web page, not in console. There is only possibility to change values, not to see them. As these fields contain sensitive data, their values are encrypted on the router;
• Customer web page must be opened using secure SSL connection (https) to change field values;

TODO

Usage

TODO

PayPal

Not supported at the moment, in development.