You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add following keys to `.env` file and updated the details ([view more about configuration](https://support.bitpay.com/hc/en-us/articles/115003001063-How-do-I-configure-the-PHP-BitPay-Client-Library-)):
45
45
46
-
note: BITPAY_TOKEN_LABEL can be any name, but can not have spaces
By default package is capable of handling of webhook requests. Bitpay payment status updates are completely based on webhooks. Whenever webhook is received from server, `BitpayWebhookReceived` event is dispatched. You just need to provide a listener for this event.
55
+
By default, package is capable of handling of webhook requests. Bitpay payment status updates are completely based on webhooks. Whenever webhook is received from server, `BitpayWebhookReceived` event is dispatched. You just need to provide a listener for this event.
59
56
60
57
You can add your listener as below,
61
58
```php
@@ -129,7 +126,7 @@ class EventServiceProvider extends ServiceProvider{
129
126
+ SIN (Service Identification Number) for your client will be created to uniquely identify requests from your server.
130
127
+ By using SIN **new Token and Pairing Code** will be created for your client on bitpay server and will be shown on your console output.
131
128
+ Token will be used for all future request to bitpay and will automatically be copied to your `.env` file.
132
-
+ Based on environment you set**TEST/LIVE**, command will provide URL to approve your client and you need to copy and search Pairing Code on bitpay server & approve it.
129
+
+ Based on environment you set**TEST/LIVE**, command will provide URL to approve your client, andthen you need to copy and search Pairing Code on bitpay server & approve it.
0 commit comments