Download the PHP package phpcommerce/ratepay without Composer

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

Informations about the package ratepay

php-ratepay

Example for a RatePAY checkout

You need to send at least the following gateway operations:

PAYMENT_INIT -> PAYMENT_REQUEST -> PAYMENT_CONFIRM

Triggering a payment change request

Triggering a confirmation deliver request

RatePAY Gateway Endpoints

The RatePAY Gateway system is implemented as a XML over HTTP webservice. It can be accessed via SSL:

RatePAY gateway operations

Gateway operation Mandatory / Optional Purpose
PAYMENT_INIT M Initialize the transaction and get a valid transaction-id.
PAYMENT_QUERY full O Check the customer and order details, perform a configurable risk scoring, retrieve the payment products permitted in the given context. The PAYMENT_QUERY full can be booked with a guaranteed acceptance. This means that all products given back will be accepted by a following PAYMENT_REQUEST.
PAYMENT_REQUEST M Check the customer and order details, perform risk scoring, return either customer acceptance or rejection.
PAYMENT_CONFIRM M (if response of the PAYMENT_REQUEST is positive) Finalize the payment process.
CONFIRMATION_DELIVER (“CD”) M (if order has not been cancelled) Immediately after the ordered goods have been delivered to the customer, the merchant must send a Confirmation Deliver message to the RatePAY Gateway.
PAYMENT_CHANGE cancellation O Merchant cancels some or all items of the order
PAYMENT_CHANGE return O Merchant returns some or all items of the order
PAYMENT_CHANGE change-order O Merchant or customer adds items to the order
PAYMENT_CHANGE credit O Merchant adds a credit (discount) or debit (adjustment charge) to the order
CONFIGURATION_REQUEST O Retrieve the stored configuration parameters for a certain merchant profile.
CALCULATION_REQUEST O Provides an installment plan depending on the request parameters and stored parameters of the merchant profile.

Please note: The gateway operations are exposed through the RatepayBroker object.

JMS Serializer Library Usage Note

This library makes heavy use of the JMS-Serializer library which itself makes heavy ues of the doctrine annotation features.

To use the library in a standalone environment make sure to register the serializer source directory in the doctrine annotation registry.

Appendix: Result Codes

The following result codes are only for internal reference in the library and are exposed via the the RejectionException, TechnicalException and WarningException if you use the RatepayBroker object.

Operation Success Rejection Technical Error Warning Additional Information
PAYMENT_INIT 350 - 150 - -
PAYMENT_QUERY 402 401 150 405 The PAYMENT_QUERY needs a different evaluation. To determine if a following PAYMENT_REQUEST will be successful, the corresponding product has to be available.
PAYMENT_REQUEST 402 401 150 405 -
PAYMENT_CONFIRM 400 401 150 405 -
PAYMENT_CHANGE 403 401 150 405 -
CONFIRMATION_DELIVER 404 401 150 405 -
CALCULATION_REQUEST 502 503 150 - Note when a 503 is triggered: Although sending the same CALCULATION_REQUEST again is possible, the result will always be the same. This result indicates a request with wrong parameters.
CONFIGURATION_REQUEST 500 - 150 - -

All versions of ratepay with dependencies

PHP Build Version
Package Version
Requires jms/serializer Version ~1.1
guzzlehttp/guzzle Version ~6.1
psr/log Version ~1.0
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 phpcommerce/ratepay contains the following files

Loading the files please wait ....