Download the PHP package shakurov/coinbase without Composer

Laravel wrapper for the Coinbase Commerce API

This package is abandoned and no longer maintained. The author suggests using the antimech/coinbase package instead.

Installation

You can install the package via composer:

The service provider will automatically register itself.

You must publish the config file with:

This is the contents of the config file that will be published at config/coinbase.php:

In the webhookSecret key of the config file you should add a valid webhook secret. You can find the secret used at the webhook configuration settings on the Coinbase Commerce dashboard.

Next, you must publish the migration with:

After the migration has been published you can create the coinbase_webhook_calls table by running the migrations:

Finally, take care of the routing: At the Coinbase Commerce dashboard you must add a webhook endpoint, for example: https://example.com/api/coinbase/webhook

Usage

Charges

List charges:

Create a charge:

Show a charge:

Cancel a charge:

Resolve a charge:

Checkouts

List checkouts:

Create a checkout:

Show a checkout:

Update a checkout:

Delete a checkout:

Invoices

List invoices:

Create an invoice:

Show an invoice:

Void an invoice:

Resolve an invoice:

Events

List events:

Show an event:

Webhooks

Coinbase Commerce will send out webhooks for several event types. You can find the full list of events types in the Coinbase Commerce documentation.

Coinbase Commerce will sign all requests hitting the webhook url of your app. This package will automatically verify if the signature is valid. If it is not, the request was probably not sent by Coinbase Commerce.

Unless something goes terribly wrong, this package will always respond with a 200 to webhook requests. Sending a 200 will prevent Coinbase Commerce from resending the same event over and over again. All webhook requests with a valid signature will be logged in the coinbase_webhook_calls table. The table has a payload column where the entire payload of the incoming webhook is saved.

If the signature is not valid, the request will not be logged in the coinbase_webhook_calls table but a Shakurov\Coinbase\Exceptions\WebhookFailed exception will be thrown. If something goes wrong during the webhook request the thrown exception will be saved in the exception column. In that case the controller will send a 500 instead of 200.

There are two ways this package enables you to handle webhook requests: you can opt to queue a job or listen to the events the package will fire.

Handling webhook requests using jobs

If you want to do something when a specific event type comes in you can define a job that does the work. Here's an example of such a job:

We highly recommend that you make this job queueable, because this will minimize the response time of the webhook requests. This allows you to handle more Coinbase Commerce webhook requests and avoid timeouts.

After having created your job you must register it at the jobs array in the coinbase.php config file. The key should be the name of the coinbase commerce event type where but with the . replaced by _. The value should be the fully qualified classname.

Handling webhook requests using events

Instead of queueing jobs to perform some work when a webhook request comes in, you can opt to listen to the events this package will fire. Whenever a valid request hits your app, the package will fire a coinbase::<name-of-the-event> event.

The payload of the events will be the instance of CoinbaseWebhookCall that was created for the incoming request.

Let's take a look at how you can listen for such an event. In the EventServiceProvider you can register listeners.

Here's an example of such a listener:

We highly recommend that you make the event listener queueable, as this will minimize the response time of the webhook requests. This allows you to handle more Coinbase Commerce webhook requests and avoid timeouts.

The above example is only one way to handle events in Laravel. To learn the other options, read the Laravel documentation on handling events.

Advanced usage

Retry handling a webhook

All incoming webhook requests are written to the database. This is incredibly valuable when something goes wrong while handling a webhook call. You can easily retry processing the webhook call, after you've investigated and fixed the cause of failure, like this:

Performing custom logic

You can add some custom logic that should be executed before and/or after the scheduling of the queued job by using your own model. You can do this by specifying your own model in the model key of the coinbase config file. The class should extend Shakurov\Coinbase\Models\CoinbaseWebhookCall.

Here's an example:

License

The MIT License (MIT). Please see License File for more information.

Backers

• @antimech