Download the PHP package quellabs/canvas-payments-buckaroo without Composer

On this page you can find all versions of the php package quellabs/canvas-payments-buckaroo. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of quellabs/canvas-payments-buckaroo

Informations about the package canvas-payments-buckaroo

Buckaroo Payment Provider

A Buckaroo payment provider for the Canvas framework. Part of the Canvas payments ecosystem.

Installation

Architecture

This package sits between the Buckaroo JSON API and your application. Your application only ever touches the contracts layer — it never depends on this package directly. PaymentRouter (from quellabs/canvas-payments) discovers this package automatically via composer metadata and routes payment calls to it.

Push processing is decoupled from your application via signals. When Buckaroo posts to the push URL, the package emits a payment_exchange signal carrying a PaymentState. Your application listens for that signal and handles it.

Configuration

Create config/buckaroo.php in your Canvas application (this is done automatically on first install):

Key Required Description
website_key Yes Your Buckaroo website key, found in Plaza under My Buckaroo > Websites > {your site}
secret_key Yes Your Buckaroo secret key, generated in Plaza under Configuration > Secret Key
test_mode No Use the Buckaroo test environment (testcheckout.buckaroo.nl). Defaults to false
return_url Yes URL the shopper is redirected to after a completed or pending payment
return_url_cancel Yes URL the shopper is redirected to after cancelling payment
return_url_error No URL for technical errors during payment. Falls back to return_url_cancel if empty
return_url_reject No URL for acquirer-rejected payments. Falls back to return_url_cancel if empty
push_url Yes Full URL Buckaroo POSTs push notifications to. Must be publicly reachable
default_culture No BCP 47 culture tag for hosted page language and email templates. Defaults to nl-NL

Buckaroo Plaza configuration

In addition to config/buckaroo.php, configure the following in Buckaroo Plaza:

Key differences from MultiSafepay

Authentication

Buckaroo uses HMAC-SHA256 request signing. Every request carries an Authorization header:

The signing string is: websiteKey + METHOD + urlencode(host+path, lowercase) + timestamp + nonce + base64(md5(body))

Amounts

Buckaroo amounts are decimal floats (10.00 = €10.00), not minor units. The driver converts automatically — PaymentRequest::$amount stays in minor units (e.g. 1000 for €10.00).

Transaction identity

Buckaroo issues its own transaction key (Key in the response, 32-char hex). This key is stored as transactionId in PaymentState and InitiateResult. Your order reference is passed as Invoice and returned as BRQ_INVOICENUMBER in the return URL.

Push vs webhook

Buckaroo's push sends a JSON body (not form-encoded like MultiSafepay):

The controller reads Transaction.Key from the JSON body and falls back to brq_transactions query param for legacy configurations.

Return URL parameters

Buckaroo appends these to the configured ReturnURL:

Parameter Value
BRQ_TRANSACTIONS Buckaroo transaction key (our transactionId)
BRQ_INVOICENUMBER Your Invoice reference
BRQ_STATUSCODE Numeric status code (informational only)

We always call the API for the authoritative status and do not rely on the return URL params.

Status codes

Code Meaning Maps to
190 Success — payment completed PaymentStatus::Paid
790–793 Pending — awaiting processor/consumer PaymentStatus::Pending
890 Cancelled by consumer PaymentStatus::Canceled
490–492 Failure PaymentStatus::Failed
690 Rejected by Buckaroo or acquirer PaymentStatus::Failed

Usage

Initiating a payment

Handling refunds

Listening for payment state changes

License

MIT

All versions of canvas-payments-buckaroo with dependencies

PHP Build Version
Package Version
Requires php Version ^8.2
ext-curl Version *
symfony/http-client Version ^7.0 || ^8.0
quellabs/support Version *
quellabs/contracts Version *
quellabs/canvas-payments-contracts Version *
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package quellabs/canvas-payments-buckaroo contains the following files

Loading the files please wait ...