Download the PHP package dp-soft-co/payments without Composer

Dpsoft Payment Gateways

A Laravel package for integrating multiple payment gateways with a unified API. Supports 19+ gateways including PayPal, Paymob, Kashier, Fawry, Fawaterk, HyperPay, Thawani, Tap, Opay, Paytabs, Binance, PerfectMoney, NowPayments, Payeer, Telr, Clickpay, MyFatoorah, Stripe, and E-Wallets.

Supported Gateways

Installation

Publish Vendor Files

Configuration

All gateway settings are driven by environment variables. After publishing, edit config/dpsoft-payments.php and add the keys you need to your .env.

PayMob

Fawaterk (API v3)

Fawaterk v3 uses OAuth client credentials for API calls and Vendor API Key for hash signing (iframe & webhooks).

Endpoints used:

• POST /api/v3/createTransaction — create payment (OAuth Bearer token)
• POST /api/v3/getTransactionData — verify payment (OAuth Bearer token)
• POST /oauth/token — obtain access token (client credentials grant)

Webhook hash verification:

• Paid webhook: transactionHashKey = HMAC-SHA256("TransactionId={id}&TransactionKey={key}&PaymentMethod={method}", vendor_api_key)
• Failed webhook: hashKey = same formula as above
• Cancel webhook: hashKey = HMAC-SHA256("referenceId={refId}&PaymentMethod={method}", vendor_api_key)
• Legacy v2 webhooks still supported via hashKey with InvoiceId/InvoiceKey

Iframe hash:

• hashKey = HMAC-SHA256("Domain={your_domain}&ProviderKey={provider_key}", vendor_api_key)
• Uses fawaterkCheckoutV2() and fawaterkPlugin.js

Kashier

HyperPay

Fawry

PayPal

Stripe

Thawani

Tap

Opay

Paytabs

Binance Pay

NowPayments

Payeer

PerfectMoney

Telr

Clickpay

MyFatoorah

How To Use

Standard Controller Example

The following Laravel controller pattern works with every gateway supported by the package. Store the gateway class name used to create the invoice so the callback can use the same gateway. Replace Invoice, the payment view, and success/failure routes with your application equivalents.

Render gateway HTML only when it comes directly from the package response:

Register the verification route:

CSRF Protection

Payment gateways send POST callbacks from an iframe or external page and will not include the Laravel CSRF token. You must exclude the verification route from CSRF validation:

• Laravel 11 (bootstrap/app.php):

• Laravel 10 (app/Http/Middleware/VerifyCsrfToken.php):

Adjust the wildcard to match your actual route path and any language prefix (e.g. *payments/verify*).

Gateway-specific source values

Most other gateways do not use source; passing null is valid.

Test Cards

Fawaterk (Staging)

Other Gateways

• PayMob — Test phone: 01010101010, PIN & OTP: 123456
• Kashier
• Fawry
• Thawani
• Tap
• Opay
• PayTabs

License

MIT License. See LICENSE file for details.