Download the PHP package karser/payum-saferpay without Composer

On this page you can find all versions of the php package karser/payum-saferpay. 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 karser/payum-saferpay

Informations about the package payum-saferpay

Saferpay Payum Plugin

Build Status Scrutinizer Code Quality Code Coverage Total Downloads

Introduction

This plugin implements Saferpay specification v1.10, including all features from e-commerce and business licenses. Saferpay e-commerce license provides access to Payment Page interface only. Saferpay Business license provides Transaction Interface, recurring payments, storing cards aliases and etc. For more detailed comparison please refer to Licensing options and Supported payment methods per interface.

Transaction Interface provides two options: an iframe (similar to Payment Page) and submitting the card data directly. The last option is available only if you are PCI compliant.

Here is how Payment Page interface looks like:

Here is how Transaction interface looks like:

Requirements

Features

This plugin supports

All features are covered with tests. You can find useful examples in functional tests.

Installation

Configuration

With PayumBundle (Symfony)

First register the gateway factory in your services definition:

Then configure the gateway:

You can use General test account credentials or create personal test account here

With Payum

Configure the routes

You can include the default Payum Bundle's routes, although only these routes are actually required by this plugin:

Usage

Capture example

Make sure you defined Payment and Token entities like it is described here

Recurring Payments with the referenced transactions Method

  1. Capture payment with Recurring or Installment option:

  2. Capture a new transaction by providing a reference to the previous one:

Recurring Payments using an alias

  1. Obtaining the Alias: The user will have to enter their card details in an iframe.

  2. Capture a new transaction by providing an alias id:

Change Payload Locale

  1. Create a custom extension (If you're using the symfony bundle):

  2. Create service:

Additional Configuration

Depending on given interface, there are several optional options available.

Example:

Payment Page interface

Key Description
config_set This parameter let you define your payment page config (PPConfig) by name. If this parameters is not set, your default PPConfig will be applied if available. When the PPConfig can't be found (e.g. wrong name), the Saferpay basic style will be applied to the payment page.
payment_methods Used to restrict the means of payment which are available to the payer for this transaction. If only one payment method id is set, the payment selection step will be skipped.
wallets Used to control if wallets should be enabled on the payment selection page and to go directly to the given wallet (if exactly one wallet is filled and PaymentMethods is not set).
notification_merchant_email Email addresses to which a confirmation email will be sent to the merchants after successful authorizations.
notification_payer_email Email address to which a confirmation email will be sent to the payer after successful authorizations.
styling_css_url Deprecated
styling_content_security_enabled When enabled, then ContentSecurity/SAQ-A is requested, which leads to the CSS being loaded from the saferpay server.
styling_theme This parameter let you customize the appearance of the displayed payment pages. Per default a lightweight responsive styling will be applied.If you don't want any styling use 'NONE'.
payer_note Text which will be printed on payer's debit note. Supported by SIX Acquiring. No guarantee that it will show up on the payer's debit note, because his bank has to support it too. Please note that maximum allowed characters are rarely supported. It's usually around 10-12.

Transaction interface

Key Description
config_set This parameter let you define your payment page config (PPConfig) by name. If this parameters is not set, your default PPConfig will be applied if available. When the PPConfig can't be found (e.g. wrong name), the Saferpay basic style will be applied to the payment page.
payment_methods Used to restrict the means of payment which are available to the payer for this transaction. If only one payment method id is set, the payment selection step will be skipped.
styling_css_url Deprecated
styling_content_security_enabled When enabled, then ContentSecurity/SAQ-A is requested, which leads to the CSS being loaded from the saferpay server.
styling_theme This parameter let you customize the appearance of the displayed payment pages. Per default a lightweight responsive styling will be applied. If you don't want any styling use 'NONE'.
payer_note Text which will be printed on payer's debit note. Supported by SIX Acquiring. No guarantee that it will show up on the payer's debit note, because his bank has to support it too. Please note that maximum allowed characters are rarely supported. It's usually around 10-12.

Testing

ToDo

Credits

License

This plugin is under the MIT license. For the whole copyright, see the LICENSE file distributed with this source code.

All versions of payum-saferpay with dependencies

PHP Build Version
Package Version
Requires php Version ^7.3 || ^8.0
payum/core Version ^1.6
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 karser/payum-saferpay contains the following files

Loading the files please wait ....