quellabs/canvas-payments-buckaroo
Composer 安装命令:
composer require quellabs/canvas-payments-buckaroo
包简介
Buckaroo payment gateway integration for the Canvas PHP framework
README 文档
README
A Buckaroo payment provider for the Canvas framework. Part of the Canvas payments ecosystem.
Installation
composer require quellabs/canvas-payments-buckaroo
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.
Your Application
│
▼
PaymentRouter (quellabs/canvas-payments — discovery + routing)
│
▼
PaymentInterface (quellabs/canvas-payments-contracts)
│
▼
Buckaroo Driver (this package — implements the interface)
│
▼
BuckarooGateway (raw Buckaroo JSON API calls)
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):
return [ 'website_key' => '', 'secret_key' => '', 'test_mode' => false, 'return_url' => 'https://example.com/order/thankyou', 'return_url_cancel' => 'https://example.com/order/cancelled', 'return_url_error' => 'https://example.com/order/error', 'return_url_reject' => 'https://example.com/order/rejected', 'push_url' => 'https://example.com/webhooks/buckaroo', 'default_culture' => 'nl-NL', ];
| 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:
- Push URL: My Buckaroo > Websites > {your site} > Push Settings — set to your
push_urlvalue - Return URLs are per-request (sent in each transaction); Plaza values serve as fallback only
Key differences from MultiSafepay
Authentication
Buckaroo uses HMAC-SHA256 request signing. Every request carries an Authorization header:
hmac <websiteKey>:<base64(HMAC-SHA256(signingString, secretKey))>:<nonce>:<timestamp>
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):
{
"Transaction": {
"Key": "<32-char key>",
"Status": {
...
},
...
}
}
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
use Quellabs\Payments\Contracts\PaymentInterface; use Quellabs\Canvas\Controllers\BaseController; use Quellabs\Payments\Contracts\PaymentRequest; use Quellabs\Payments\Contracts\PaymentInitiationException; class CheckoutController extends BaseController { public function __construct(private PaymentInterface $router) {} /** * @Route("...") */ public function checkout(): Response { $request = new PaymentRequest( paymentModule: 'bkr_ideal', amount: 999, // in minor units — €9.99 currency: 'EUR', description: 'Order #12345', reference: 'ORDER-12345', issuerId: 'INGBNL2A', ); try { $result = $this->router->initiate($request); return $this->redirect($result->redirectUrl); } catch (PaymentInitiationException $e) { // handle error } } }
Handling refunds
use Quellabs\Payments\Contracts\RefundRequest; use Quellabs\Payments\Contracts\PaymentRefundException; // Full refund (omit amount) $request = new RefundRequest( paymentReference: $state->transactionId, paymentModule: 'bkr_ideal', amount: null, // null = full refund currency: 'EUR', description: 'Full refund for order #12345', ); // Partial refund $request = new RefundRequest( paymentReference: $state->transactionId, paymentModule: 'bkr_ideal', amount: 500, // in minor units — €5.00 currency: 'EUR', description: 'Partial refund for order #12345', ); try { $result = $this->router->refund($request); echo $result->refundId; // Buckaroo refund transaction Key } catch (PaymentRefundException $e) { // handle error }
Listening for payment state changes
use Quellabs\Canvas\Annotations\ListenTo; use Quellabs\Payments\Contracts\PaymentState; use Quellabs\Payments\Contracts\PaymentStatus; class OrderService { /** * @ListenTo("payment_exchange") */ public function onPaymentExchange(PaymentState $state): void { match ($state->state) { PaymentStatus::Paid => $this->markPaid($state->transactionId, $state->valuePaid), PaymentStatus::Canceled => $this->markCanceled($state->transactionId), PaymentStatus::Refunded => $this->handleRefund($state), PaymentStatus::Failed => $this->markFailed($state->transactionId), default => null, }; } }
License
MIT
quellabs/canvas-payments-buckaroo 适用场景与选型建议
quellabs/canvas-payments-buckaroo 是一款 基于 PHP 开发的 Composer 扩展包,目前已累计 0 次下载、GitHub Stars 达 0, 最近一次更新时间为 2026 年 03 月 20 日, 在 PHP 生态内属于活跃度较高的组件。
它主要适用于以下技术方向: 「payments」 「ideal」 「buckaroo」 「payment gateway」 「canvas」 「netherlands」 等业务场景。在实际项目中,围绕这些方向常见需要落地的问题包括:接口对接、性能调优、并发安全、与既有框架(Laravel / ThinkPHP / Yii / Webman 等)的兼容适配,以及生产环境的日志埋点与稳定性保障。
我们在过去多个企业项目中使用过 quellabs/canvas-payments-buckaroo 或与其功能相近的方案,如果你在选型或落地过程中遇到问题,例如 版本兼容、二次改造、私有化封装、与内部系统对接、生产 BUG 排查,欢迎联系我们协助评估。
基于 quellabs/canvas-payments-buckaroo 在你已有业务上做功能扩展、字段裁剪、UI 适配、与内部账号 / 权限 / 日志系统的深度对接。
线上偶发问题、内存泄漏、慢查询、并发异常等排查修复;针对高流量场景做缓存、队列、索引层面的调优。
承接完整的项目从需求 → 设计 → 开发 → 上线 → 长期运维;也可按月提供技术保姆服务。
与 quellabs/canvas-payments-buckaroo 相关的其它包
同方向 / 同关键字的高下载量 PHP Composer 包推荐,方便对比选型:
Buckaroo BPE3 API client for PHP. PSR-0 Compliant.
iDeal payment gateway for Omnipay
iDeal driver for the Omnipay PHP payment processing library
CardGate API client library for PHP
Allows customers sign up for recurring and one-time payments with Stripe, perfect for orders, donations, subscriptions, and events. Create simple payment forms in seconds easily without coding. For Craft CMS 3.x
Buckaroo BPE3 API client for PHP. PSR-4 Compatible.
统计信息
- 总下载量: 0
- 月度下载量: 0
- 日度下载量: 0
- 收藏数: 0
- 点击次数: 27
- 依赖项目数: 0
- 推荐数: 0
其他信息
- 授权协议: MIT
- 更新时间: 2026-03-20