armorpayments/armorpayments-php
Composer 安装命令:
composer require armorpayments/armorpayments-php
包简介
A PHP client library for interacting with the Armor Payments API
README 文档
README
This is intended to be a clean, idiomatic client for the Armor Payments API. This will handle generating the authenticated headers and constructing the properly nested request URI, as well as parsing any response JSON for you.
Installation
You can install using composer or from source.
Composer
If you don't have Composer install it:
$ curl -s https://getcomposer.org/installer | php
Add this to your composer.json:
{
"require": {
"armorpayments/armorpayments-php": "*"
}
}
Refresh your dependencies:
$ php composer.phar update
Then make sure to require the autoloader:
<?php require_once(__DIR__ . '/vendor/autoload.php'); ...
Source
Download the armor-payments-php source:
$ git clone https://github.com/Armor-Payments/armor-payments-php
And then require all bootstrap files:
<?php require_once("/path/to/armor-payments-php/lib/ArmorPayments/ArmorPayments.php"); ...
Quickstart
curl -s http://getcomposer.org/installer | php
echo '{
"require": {
"armorpayments/armorpayments-php": "*"
}
}' > composer.json
php composer.phar install
curl https://raw.githubusercontent.com/Armor-Payments/armor-payments-php/master/Example.php > Example.php
# Replace api_key and api_secret values with your own credentials
echo '<?php
$api_key = "ENTER_YOUR_API_KEY_HERE";
$api_secret = "ENTER_YOUR_API_SECRET_HERE";' > api_credentials.php
php Example.php
Usage
The Armor Payments API is REST-ish and nested, so the client relies on chaining. We return an object (or array of objects) decoded from the JSON response if possible.
require_once 'path_to_library_install/lib/ArmorPayments/ArmorPayments.php' $client = new \ArmorPayments\Api('your-key', 'your-secret', $should_use_sandbox); // There are two top-level resources: accounts and shipmentcarriers // Querying users and orders requires an account_id $client->accounts()->all(); $client->accounts()->get($account_id); $client->shipmentcarriers()->all(); $client->shipmentcarriers()->get($carrier_id); // From accounts, we chain users, orders, bank accounts $client->accounts()->users($account_id)->all(); $client->accounts()->users($account_id)->get($user_id); $client->accounts()->orders($account_id)->all(); $client->accounts()->orders($account_id)->get($order_id); $client->accounts()->bankaccounts($account_id)->all(); $client->accounts()->bankaccounts($account_id)->get($bank_account_id); // From orders, many things chain: documents, notes, disputes, shipments, // payment instructions, order events $client->accounts()->orders($account_id)->documents($order_id)->all(); $client->accounts()->orders($account_id)->documents($order_id)->get($document_id); $client->accounts()->orders($account_id)->notes($order_id)->all(); $client->accounts()->orders($account_id)->notes($order_id)->get($note_id); $client->accounts()->orders($account_id)->disputes($order_id)->all(); $client->accounts()->orders($account_id)->disputes($order_id)->get($dispute_id); $client->accounts()->orders($account_id)->shipments($order_id)->all(); $client->accounts()->orders($account_id)->shipments($order_id)->get($shipment_id); $client->accounts()->orders($account_id)->paymentinstructions($order_id)->all(); $client->accounts()->orders($account_id)->orderevents($order_id)->all(); $client->accounts()->orders($account_id)->orderevents($order_id)->get($event_id); // From disputes, further things chain: documents, notes, offers $client->accounts()->orders($account_id)->disputes($order_id)->documents($dispute_id) ->all(); $client->accounts()->orders($account_id)->disputes($order_id)->documents($dispute_id) ->get($document_id); $client->accounts()->orders($account_id)->disputes($order_id)->notes($dispute_id) ->all(); $client->accounts()->orders($account_id)->disputes($order_id)->notes($dispute_id) ->get($note_id); $client->accounts()->orders($account_id)->disputes($order_id)->offers($dispute_id) ->all(); $client->accounts()->orders($account_id)->disputes($order_id)->offers($dispute_id) ->get($offer_id); // From offers, documents and notes chain $client->accounts()->orders($account_id)->disputes($order_id)->offers($dispute_id) ->documents($offer_id)->all(); $client->accounts()->orders($account_id)->disputes($order_id)->offers($dispute_id) ->documents($offer_id)->get($document_id); $client->accounts()->orders($account_id)->disputes($order_id)->offers($dispute_id) ->notes($offer_id)->all(); $client->accounts()->orders($account_id)->disputes($order_id)->offers($dispute_id) ->notes($offer_id)->get($note_id);
Some of the resource endpoints support Create/Update POST operations, and this client aims to support those as well:
$client->accounts()->create($your_data); $client->accounts()->update($account_id, $your_data); $client->accounts()->bankaccounts($account_id)->create($your_data); $client->accounts()->orders($account_id)->create($your_data); $client->accounts()->orders($account_id)->shipments($order_id)->create($your_data); $client->accounts()->orders($account_id)->documents($order_id)->create($your_data); $client->accounts()->orders($account_id)->disputes($order_id)->documents($dispute_id) ->create($your_data); $client->accounts()->orders($account_id)->disputes($order_id)->offers($dispute_id) ->documents($offer_id)->create($your_data); $client->accounts()->orders($account_id)->notes($order_id)->create($your_data); $client->accounts()->orders($account_id)->disputes($order_id)->notes($dispute_id) ->create($your_data); $client->accounts()->orders($account_id)->disputes($order_id)->offers($dispute_id) ->notes($offer_id)->create($your_data); $client->accounts()->orders($account_id)->update($order_id, $your_data); $client->accounts()->orders($account_id)->disputes($order_id)->offers($dispute_id) ->update($offer_id, $your_data); $client->accounts()->users($account_id)->create($your_data); $client->accounts()->users($account_id)->authentications($user_id)->create($your_data);
Contributing
- Fork it
- Create your feature branch (
git checkout -b my-new-feature) - Commit your changes (
git commit -am 'Add some feature') - Push to the branch (
git push origin my-new-feature) - Create new Pull Request
armorpayments/armorpayments-php 适用场景与选型建议
armorpayments/armorpayments-php 是一款 基于 PHP 开发的 Composer 扩展包,目前已累计 3.94k 次下载、GitHub Stars 达 15, 最近一次更新时间为 2014 年 11 月 03 日, 在 PHP 生态内属于活跃度较高的组件。
它主要适用于以下技术方向: 「api」 「Armor Payments」 「escrow payments」 等业务场景。在实际项目中,围绕这些方向常见需要落地的问题包括:接口对接、性能调优、并发安全、与既有框架(Laravel / ThinkPHP / Yii / Webman 等)的兼容适配,以及生产环境的日志埋点与稳定性保障。
我们在过去多个企业项目中使用过 armorpayments/armorpayments-php 或与其功能相近的方案,如果你在选型或落地过程中遇到问题,例如 版本兼容、二次改造、私有化封装、与内部系统对接、生产 BUG 排查,欢迎联系我们协助评估。
基于 armorpayments/armorpayments-php 在你已有业务上做功能扩展、字段裁剪、UI 适配、与内部账号 / 权限 / 日志系统的深度对接。
线上偶发问题、内存泄漏、慢查询、并发异常等排查修复;针对高流量场景做缓存、队列、索引层面的调优。
承接完整的项目从需求 → 设计 → 开发 → 上线 → 长期运维;也可按月提供技术保姆服务。
与 armorpayments/armorpayments-php 相关的其它包
同方向 / 同关键字的高下载量 PHP Composer 包推荐,方便对比选型:
Dealing with payments through the Egyptian payment gateway PayMob
Librería para la gestión sencilla de pagos mediante TPV Redsys y Paypal
A PSR-7 compatible library for making CRUD API endpoints
Scanpay module for Magento 2
Official Safaricom Daraja M-Pesa integration for Laravel built on ysg/payment-core.
Официальный PHP SDK для платёжного шлюза Oblodai: приём платежей, выплаты, статические кошельки, вебхуки.
统计信息
- 总下载量: 3.94k
- 月度下载量: 0
- 日度下载量: 0
- 收藏数: 15
- 点击次数: 31
- 依赖项目数: 0
- 推荐数: 0
其他信息
- 授权协议: MIT
- 更新时间: 2014-11-03