Support for regional endpoints

This release adds the parameters for altering the target authorize api region.

Adding support for ApplicationFeatures

Summary

• Adding support for ApplicationFeatures Documentation

Adding Support for Multiple Models & Application Priority Data

v2.6 Release Notes - https://github.com/Lenddo/php-lenddo/releases/tag/v2.6

Summary

• Adding Support for ApplicationMultipleScores Documentation
• Adding support for Authorize API & PriorityData Documentation

Adding support for e-mail probe in Verification Class

With this light release we now support e-mail verification via the Verification class.

To utilize this new probe simply perform the following:

$verification = new Lenddo\Verification();
$verification->setEmail("support@lenddo.com");

Please read the relevant documentation here

Adding support for ExtraApplicationData

v2.4 adds support for the new ExtraApplicationData endpoint. With this functionality you can submit data to Lenddo which may assist with the scoring and verification algorithms.

To read more information about this please refer to the documentation here.

Adding utility to test your webhook implementation

New with this release is the ability to reliably test your webhook implementation in multiple scenarios. After integration with Webhooks, you will probably want to test your platform to ensure it works as you expect. We found multiple partners coping with this in different ways so we've expanded our SDK to provide a simple class which you can configure and use against your own implementation.

This class will call your implementation and expect a response that our own systems would expect. This means you can reliably understand how your system will interact with ours.

• Read the documentation here

If you are not currently using webhooks but would like to, please contact your Lenddo representative.

Adding Verification Support for Whitelabel Client

This is a backward compatible release which now allows for consumers of the WhiteLabel product of this SDK to now also utilize Lenddo Verification Services.

• Read the updated documentation here

If you are unfamiliar with the WhiteLabel client you can begin reading about it here

• WhiteLabel Client

Documentation Updates

This is a minor release that does not change anything in the code. Instead it incorporates some changes to the documentation based on some feedback we've had and includes one new downstream feature added to the verification service. Lenddo will now return phone verification results along with the verification results response object.

The update can be found here: /docs/verification_response.md.

Better Exception Management

Announcing Lenddo PHP SDK v2.1.

This release adds 5 new exception classes that make communicating back exceptions occurring during a request easier to comprehend. Previously to utilize these functions you had to rely on the Guzzle exception class.

documentation
A summary and explanation of these exceptions can be found at docs/handling_exceptions.md

backward compatibility
If you rely on guzzle-specific error features you can still find them under the $e->getPrevious() method call, assuming $e is the exception. By calling this method you will retrieve the guzzle exception that was originally thrown.

Extended legacy support, simpler integration.

php-lenddo v2.0 Introduction

This upgrade marks a significant upgrade to the core to allow further compatibility with more systems despite their configuration. We're no longer just compatible with PHP >=5.5 or Guzzle 6.

We're now compatible down to PHP 5.3, and Guzzle versions 3, 4, 5, and 6.

The new PHP SDK Release has a major version bump due to some backward compatibility breaking changing which will be detailed below. We highly recommend upgrading your version to 2.0, please reach out to Lenddo should you require assistance doing so. You can begin at the Backward Compatibility Breaks section attached to this release notice.

Enhanced Documentation

The documentation has now been segmented and enhanced now that it's grown to a significant size. This move is to make the documentation easier to digest. Take a Look

Certificate Authority Inclusion

To alleviate some issues with SSL Certs not always being available on target machines we're now including the certificate authority bundle provided by Mozilla. This can be found here: https://curl.haxx.se/ca/cacert.pem

Backward Compatibility Breaks

Previously the response of the REST clients would be a GuzzleHTTP Response Object. This is still available to you but it's nested within a response handler. This change was necessary since we now support many versions going back to Guzzle version 3.

The change is favorable however since you will no longer need to extended chaining introduced by Guzzle to get the data you really want.

We've abstracted the response object by using a interface-bound classes which exposes the following functions:

• getBody( $parsed = true )
• getStatusCode()
• guzzleResponse()
• guzzleRequest()

The primary changes here being the object which is returned and the body parsing.

Body Parsing

If you were using the old method of json_decode($response->getBody()->getContents()); you can now simply perform a $response->getBody(); call instead. If you do not want the body to be parsed, simply do the following: $response->getBody(false)

Take a look at the Service Client and Whitelabel client documentations to see how the code should look with v2.0.

Accessing the response object

The object which was previously returned as $response is now returned as $response->guzzleResponse()