Download the PHP package theodenhollander/docdatapayments without Composer

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

Informations about the package docdatapayments

Docdata Payments class

About

PHP Docdata Payments is a (wrapper)class to communicate with Docdata Payments. Forked from Tijsverkoyen, up-to-date with api 1.2, logging interface and a determination whether an order is paid

Extra

Forked from Tijsverkoyen Extra features:

Logging system

Interface to get extra information of the soap requests and responses

Api 1.2

Up-to-date with docdata

Class Paid Level

Docdata document: 733126_Integration_manual_Order_Api_1-1.pdf Chapter: 7.4 Determining whether an order is paid Determining whether an order is paid Different merchants can have different ways of determining when they consider an order “paid”, the totals in the status report are there to help make this decision. Keep in mind that the status report never reports about money actually having been transferred to a merchant, so it is not a complete guarantee that a payment has been finished in that sense. Using the totals to determine a level of confidence:

Quick Route:

 Another option is to see whether the sum of “total shopper pending”, “total acquirer pending”
 and “total acquirer authorized” matches the “total registered sum”.
 his implies that everyone responsible has indicated that they are going to make the payment
 and that the merchant is trusting that everyone will indeed make this.
 While this route will be faster, it does also have the risk that some payments
 will actually not have been made.

Balanced route: Depending on the merchant's situation, it can be a good option to only refer to certain totals.

 For instance, if the merchant only makes use of credit card payments it could be a good route to only look at
 “Total acquirer approved”, since this will be rather safe but quicker than looking at the captures.
 If the merchant does not want to rely on the supplied totals, they can of course also define their
 decision making on the actual authorization, capture and refund data which is also supplied in the
 status report and look at the payment method used.

Safe Route:

 The safest route to check whether all payments were made is for the merchants to refer to the
 “Total captured” amount to see whether this equals the “Total registered amount”.
  While this may be the safest indicator, the downside is that it can sometimes
  take a long time for acquirers or shoppers to actually have the money transferred and it can be captured.

License

PHP Docdata Payments is BSD licensed.

Documentation

The class is well documented inline. If you use a decent IDE you'll see that each method is documented with PHPDoc.

All versions of docdatapayments with dependencies

PHP Build Version
Package Version
Requires php Version >=5.3.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 theodenhollander/docdatapayments contains the following files

Loading the files please wait ....