Download the PHP package bsecure/bsecure-payments without Composer
On this page you can find all versions of the php package bsecure/bsecure-payments. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download bsecure/bsecure-payments
More information about bsecure/bsecure-payments
Files in bsecure/bsecure-payments
Package bsecure-payments
Short Description bSecure Payment Plugin is a Php library that allows you to securely process your payments. This plugin instantly creates a form that adheres to PCI, HIPAA, GDPR, or CCPA security requirements.
License MIT
Homepage https://github.com/bSecureCheckout/bsecure-laravel
FAQ
Example:
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 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.
Informations about the package bsecure-payments
bSecure Payments
bSecure Payments is a library that allows you to securely process your payments. This plugin instantly creates a form that adheres to PCI, HIPAA, GDPR, or CCPA security requirements.\ It is built for desktop, tablet, and mobile devices and is continuously tested and updated to offer a frictionless payment experience for your e-commerce store.
About bSecure Payment Plugin
This Payment Gateway Integration Guide is a technical integration document for merchants to integrate with bSecure Payment Plugin allowing their customers to perform e-commerce transactions over the internet.\ It guides merchants on how to use various functionality of the bSecure. The Merchant can enable credit card payments over their e-commerce website with this integration:
Who Should Read This Guide
The document is intended for application developers and business analysts of merchants to allow them to integrate effectively with the bSecure Payment Plugin.
Merchant Setup Process
In order to process online payments using the bSecure Payment Plugin, the merchant needs to be registered on bSecure Builder Portal. \ The below process assumes that the merchant has been registered and all the parameters related to the merchant have been configured.\ Once merchant has signed up for bSecure Builder Portal and get its payment gateway configured, the merchant will be in a position to perform test transaction using the sample code provided. Once the sample transaction has been successfully processed it indicates that all the required systems have been configured correctly and the merchant is ready to go.
Getting Your Credentials
- Go to Builder Portal
- App Integration >> Sandbox / Live
- Copy Client Id from App Integration tab and save it in a secure file.
- Copy Client Secret from App Integration tab and save it in a secure file.
- Copy Store Slug from App Integration tab and save it in a secure file.
- Get Merchant Id from Builder Portal
Installation
You can install the package via composer
composer require bsecure/bsecure-payments
Prerequisites
PHP 7.2.5 and above
Dependencies
"guzzlehttp/guzzle": "^7.2"
Usage
Configuration
bSecure Payments
Add provider for bSecure payments in app.php
bSecure\Payments\PaymentServiceProvider::class
Add alias
'BsecurePayments' => bSecure\Payments\BsecurePayments::class
Publish the language file.
php artisan vendor:publish --provider="bSecure\Payments\PaymentServiceProvider"
It will create a vendor/bSecure folder inside resources/lang folder. If you want to customize the error messages your can overwrite the file.
Publish the configuration file
php artisan vendor:publish --provider="bSecure\Payments\PaymentServiceProvider" --tag="config"
A file (bSecure.php) will be placed in config folder.
a) Setting up a transaction:
The bSecure Payment Plugin will receive an HTTP POST request from the merchant website which will contain the merchant authentication details along with the transaction details. The Payment Plugin will inquire the required details from the customer and process transaction:
Transaction Details
Customer Details
Customer Address Details
Examples
Create Transaction
In response createOrder(), will return order expiry, checkout_url, order_reference and merchant_order_id.
If you are using a web-solution then simply redirect the user to checkout_url
If you have Android or IOS SDK then initialize your native app's webview with 'checkout_url' and provide order_reference to it for url matching
Once transaction is created you will be able to process your checkout.
Callback on Order Placement
Once the order is successfully placed, bSecure will redirect the customer to the url you mentioned in “Checkout redirect url” in your environment settings in Partners Portal, with one additional param “order_ref” in the query string.
Order Updates
By using order_ref you received in the "Callback on Order Placement" you can call below method to get order details.
Order Status Change Webhook
Whenever there is any change in order status or payment status, bSecure will send you an update with complete order details (contents will be the same as response of Order Updates) on the URL you mentioned in Checkout Order Status webhook in your environment settings in Partners Portal. (your webhook must be able to accept POST request).
In response of "Order Updates" you will recieve complete details of your order in below mentioned format:
Managing Orders and Payments
Payment Status
| ID | Value | Description |
|---|---|---|
| 0 | Pending | Order placed. But payment is awaiting for fulfillment by the customer. |
| 1 | Completed | Order fulfilled, placed and payment has also been received. |
| 2 | Failed | Payment failed or was declined or maximum attempt for payment request reached. |
Order Status
| ID | Value | Description |
|---|---|---|
| 1 | Created | Order created by merchant |
| 2 | Initiated | Customer landed on bSecure checkout URL. Order is awaiting fulfillment. |
| 3 | Placed | Customer successfully placed the order |
| 4 | Awaiting Confirmation | Customer successfully placed the order, but is awaiting for customer confirmation to authenticate the transaction. |
| 5 | Canceled | Customer cancelled the order at the time of confirmation. |
| 6 | Expired | Order not processed within expected time frame. timeframe |
| 7 | Failed | Max payment attempt reached |
| 8 | Awaiting Payment | Customer successfully placed the order, but is payment is due or awaiting payment |
Changelog
Please see CHANGELOG for more information what has changed recently.
License
The MIT License (MIT). Please see License File for more information.
Contributions
"bSecure – Your Universal Checkout" is open source software.
