Difference between revisions of "NATS4 Bit-Pay"

From TMM Wiki
Jump to navigationJump to search
Line 11: Line 11:
 
'''Note''': If you don't see Bit-Pay, [http://clients.toomuchmedia.com put in a support ticket], as you may need an updated version of [[NATS]].
 
'''Note''': If you don't see Bit-Pay, [http://clients.toomuchmedia.com put in a support ticket], as you may need an updated version of [[NATS]].
  
Once you have added the Biller you will be able to edit biller-specific account information by clicking the pencil icon next to Bit-Pay labeled, "Edit Bit-Pay Account Info".  Details on how to create an ssl key and certificate can be found in the next section.
+
Once you have added the Biller you will be able to edit biller-specific account information by clicking the pencil icon next to Bit-Pay labeled, "Edit Bit-Pay Account Info".  You will need to create an API Token in BitPay's admin which is described in the next section
*'''SSL-KEY''' - The full path of the SSL key created on your server.
+
*'''API Token''' - The API token generated in BitPay's admin
*'''Certificate (Optional)''' - The full path of the SSL Certificate created on your server.
 
'''Note: Please make sure that the NATS Apache user has read permissions on the SSL key and Certificate files or surfers may not be directed to the Bitpay join form.'''
 
  
 
'''''Note''': Bit-Pay will not return the surfer to NATS on approval or denial, so Bit-Pay will not work with the NATS [[Ct#cascade|cascade]] feature.''
 
'''''Note''': Bit-Pay will not return the surfer to NATS on approval or denial, so Bit-Pay will not work with the NATS [[Ct#cascade|cascade]] feature.''

Revision as of 10:28, 3 October 2012

NATS 4
Members Admin
The Members Admin
View Member Details
Add Member
MySQL Auth
Mod Authn DB
Multisite Access
Member Logging
Member Password Retrieval
OpenID Connect
Mod Auth OpenIDC
ID Numbers
    Biller Instructions
NATS4 Biller List
2000Charge
2000Charge Gateway
2KCHARGE
A1Payments
Aebill
Aconti
Allopass
AltoBilling
Argus
Authorize.net
Bill1st Gateway
BillAPay Gateway
Billing Revolution
Billing United
Bit-Pay
BoaCompra
Braintree Payments
C2Bill
CardFlex
CCBill
CCBill Flexform
CCBill Web900
CashSend
CashtoCode
Centili
Centrobill
Clearcard
Clearcard IDV
Click and Buy
CoinGate
CoinPayments
CommerceGate
CurePay
DHD
DHDGateway
DIMOCO
EGatePay
ElectraCash
eMerchantPay Gateway
eMPPay.com
Epoch
Escalion
EuroBill
EPGBill.com
Ezic, Inc.
Focal Payments
FXBilling
FXBilling Native
Gateway tokens
Gigadat
Global Access
GlobalCharge
Global DPS
GoCoin
Greta 11 (G11Bill)
GTBill
GTBill GATEWAY
GXBill
ICN Ltd.
Itelebill
Jettis International
Jettis International Gateway
LocalBilling
MobiusPay
MerlinBill
NETbilling
NETbilling Native
NetCash
NetMobile
Netpay International
NoCreditCard
OrbitalPay
Password By Phone
Pay4
Pay900
Payment Network
Paygarden
Paygea
PayPal
Paysite Cash
Payspace
Payspace Gateway
Plug'n Pay
Prime Orange
Probiller
PumaPay
Rocketfuel
RocketGate
RocketGate Native
RSBilling
RSBilling Native
SafeCharge
SafeCharge Native
Secure Billing Worldwide
Secure Billing Worldwide Gateway
Secure Trading
SecurionPay
SegPay
SegPay Gateway
SOFORTdauerauftrag
Sonic Bill
StandardBill
TrustCharge
Telecom
UKash
Vendo Services
Vendo
Verotel Pro
Voxtel
VXSBill
WebBilling
Wispay
WTS
WTSeu
Zombaio
Shopping Cart Sales
Switching From Epoch to Epoch EU

Please don't test your biller setup with NATS4 Bit-Pay's test account—it won't work correctly.

Billers Admin

To add Bit-Pay to NATS4, select "Bit-Pay" from the dropdown menu list of billers next to "Setup New Biller" in the Billers Admin. Once selected, click "Add" on the right side of the page to finish adding Bit-Pay.

Note: If you don't see Bit-Pay, put in a support ticket, as you may need an updated version of NATS.

Once you have added the Biller you will be able to edit biller-specific account information by clicking the pencil icon next to Bit-Pay labeled, "Edit Bit-Pay Account Info". You will need to create an API Token in BitPay's admin which is described in the next section

  • API Token - The API token generated in BitPay's admin

Note: Bit-Pay will not return the surfer to NATS on approval or denial, so Bit-Pay will not work with the NATS cascade feature.

Setting Up at Bit-Pay

As detailed in Bit-Pay's documentation you must download openssl (http://openssl.org) in order to set up your API Access for Bit-Pay. This is required for NATS to communicate with Bit-Pay for transaction information.

Once Openssl is installed the following command can be used to generate an ssl key:

openssl genrsa -out ssl-key.pem 1024

Although it is optional, for extra security Bit-Pay recommends also creating an ssl certificate. This can be done with the following command:

openssl req -new -x509 -nodes -sha1 -days 3650 -key ssl-key.pem > ssl-cert.pem

Finally, once your key has been created, you can get your SHA-1 Fingerprint which is needed for configuration for your Bit-Pay account:

openssl x509 -in ssl-cert.pem -fingerprint -noout

Sites Admin

Bit-Pay requires no site-specific information to be modifed in your tour configuration. Instead, join options with Bit-Pay must be configured as a special join option by clicking "Set Special Payment Options" next to the site for which you would like to set up a Bit-Pay join option in the Sites Admin.

  • BITPAY Amount: The transaction amount of the join option.
  • BITPAY Currency: This is the currency that will be used to calculate the transaction amount in bitcoins based on what is set for Amount.
  • BITPAY Transaction Speed: (optional) - This is the speed at which the transaction will be processed. It is recommended that this be set to "high" for postbacks to occur instantly as other settings may take much longer for NATS to receive the postback from Bit-Pay.

Note: Bit-Pay does not postback information regarding the member's expire date so the following fields are required:

  • BITPAY Active Number: This is the number of days, hours or minutes you would like to set to be the duration of the subscription.
  • BITPAY Active Period: This is the unit of time for which you would like the Active Number to be active.

For example, a special join option with Active Number: 1 and Active Period: DAY will be a join option that expires after 1 day.