|
|
| (10 intermediate revisions by 4 users not shown) |
| Line 1: |
Line 1: |
| | + | {{NATS5 Manual |
| | + | |show_billers_section = true |
| | + | }} |
| | + | {{NATS4 Manual}} |
| | + | |
| | + | {{Test Billers Disclaimer}} |
| | + | |
| | ==Billers Admin== | | ==Billers Admin== |
| | | | |
| Line 5: |
Line 12: |
| | '''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". These details can be found in the [[NATS4_Bit-Pay#Setting Up at Bit-Pay|next section]] of this article. | + | 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''' | + | *'''API Token''' - The API token generated in BitPay's admin |
| − | *'''Certificate (Optional)'''
| + | |
| | + | '''''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.'' |
| | | | |
| | ==Setting Up at Bit-Pay== | | ==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.
| + | You will need to generate an API Key ID to act as your API Token. To generate your API Token, log into the BitPay admin (https://bitpay.com/) and click on "Account". |
| − | | + | As of August 2017 BitPay has updated their admin and you will now find this under "Integration Resources" and "Legacy API Keys" |
| − | Once Openssl is installed the following command can be used to generate an ssl key:
| + | This page allows you to generate an API Key ID. This Key is what will be your API token. To generate the token, simply click the "Add New API Key" button and it will generate the code for you. This entire code needs to be placed in the biller's admin for BitPay. |
| − | 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== | | ==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 [[NATS4 Sites Admin|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 [[NATS4 Sites Admin|Sites Admin]]. |
| | | | |
| − | '''BITPAY Amount:''' The transaction amount of the join option. | + | *'''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 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. | + | *'''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:''''' <br /> | | '''''Note: Bit-Pay does not postback information regarding the member's expire date so the following fields are required:''''' <br /> |
| | | | |
| − | '''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 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. | + | *'''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. | | For example, a special join option with Active Number: 1 and Active Period: DAY will be a join option that expires after 1 day. |
