balance 0 coinpayments adapter LiteCoin TestNET

Hello,

This support area is for the main plugin.

The support area for the CoinPayments adapter is at https://www.dashed-slug.net/forums/forum/coinpayments-net-coin-adapter-extension-support/

Having said this, please check first that you are using the latest version 2.3.4 of Bitcoin and Altcoin Wallets because there was an issue with balances on 2.3.0. Also, the callback addresses offered by the CoinPayments service require your server to be facing the internet. If you’re on a local machine behind a firewall, it will not work.

Start by making sure that you have followed the instructions and that you have entered the IPN settings correctly, then look at your IPN logs on the CoinPayments site. That should give you an indication as to what is going on. If you still cannot figure out what is wrong please continue the discussion at the support forum for the plugin extension.

Thanks and regards,
Alex

Hello,

I am using the latest version 2.3.4

Must I enter the IPN url in Coinpayments (in merchant settings)?

And HMAC or HTTP requests ? Now, I am using HTTP

I see in Coinpayments IPN sent with success

ipn url https://www.xxxxxxx.org?wallets-cp-ipn=1

ipn_mode = ‘httpauth’

status = ‘100’
status_text = ‘Deposit confirmed’
currency = ‘LTCT’
amount = ‘10.00000000’

IN API KEYS
Success

POST /api.php HTTP/1.0
Host: https://www.coinpayments.net
Connection: close
Content-Length: 142
Content-Type: application/x-www-form-urlencoded
HMAC: 7be1dcfb1857e95aaf7fd8c59f62c93123a3a29f17f64780f2c1cbbf778fea9d02c61afcdcd254a2b184777c09b195fde18269458d6589b8a63eb8461aef787b
Incap-Proxy-259: OK
X-Forwarded-For: MY SERVER IP
Incap-Client-IP: MY SERVER IP
INCAP-Req-ID: 10682687488722213

cmd=get_withdrawal_history&limit=25&start=0&newer=0&version=1&format=json&key=63d26c56671f8fad7bd2f8e950e1e10c5bee943405571130d9cda94e386735f9

All looks OK

What are the instructions ???

All settings are OK

I have maybe the solution

I am using a Litespeed Web server instead of apache who can use a different port for internet (not 80 by defaut but 8080???)

I am using now SSL with 443

Any solution ?

Regards

• This reply was modified 7 years, 9 months ago by allianse.
• This reply was modified 7 years, 9 months ago by allianse.

The installation instructions are at https://www.dashed-slug.net/bitcoin-altcoin-wallets-wordpress-plugin/coinpayments-adapter-extension/

Like you said, the problem is that you are not using port 80. I had encountered the same issue myself while developing the plugin extension, and I had to use port 80 to make it work. I believe it is a limitation of the platform.

regards,
Alex

Hello,

After verificaton, I am already with port 80, because Litespeed web server use the same port than apache.

In my IPN history in Coinpayments, I can see:

Sent with success: yes

IPN url : https://www.allianse.org?wallets-cp-ipn=1

ipn_version = ‘1.0’
ipn_id = ‘e3b352bd5cf98fc4723e31b9cc1eac7e’
ipn_mode = ‘hmac’
merchant = ’16ec45d55b6ef4668905d125029fddc8′
ipn_type = ‘deposit’
address = ‘mkXv2buWjxmGjSjqEDfywCu9PoL1icr3gp’
txn_id = ’33ec4e1bf07baf133738d8c245943160d4e4c17df71dba5af3be7768de63cd9e’
status = ‘100’
status_text = ‘Deposit confirmed’
currency = ‘LTCT’
amount = ‘1.00000000’
amounti = ‘100000000’
fee = ‘0.00500000’
feei = ‘500000’
confirms = ‘0’

But, when I go to the page https://www.allianse.org?wallets-cp-ipn=1

I see the error: IPN Mode is not HMAC

Withdrawal is OK

And balances are empty

Any solution for me ???

in API history, I have:

POST /api.php HTTP/1.0
Host: https://www.coinpayments.net
Connection: close
Content-Length: 151
Content-Type: application/x-www-form-urlencoded
HMAC: 5e7132852bb5dfe1b2b356365ed21ef49454ad9ed1114de45edab0ebac012aea958bff687a7f839b0708be670f8436cff0eb94d4fd05b644882a3f5dac10c7fd
Incap-Proxy-259: OK
X-Forwarded-For: MY IP ADRESS
Incap-Client-IP: MY IP ADRESS
INCAP-Req-ID: 298667490295350570

cmd=get_withdrawal_history&limit=25&start=0&newer=1497044688&version=1&format=json&key=63d26c56671f8fad7bd2f8e950e1e10c5bee943405571130d9cda94e386735f9

Regards

I will contact you directly by email to resolve this.

For the benefit of anyone else reading this, the issue was resolved by deactivating and reactivating the plugin.