Download the PHP package madmatt/id3global-service without Composer
On this page you can find all versions of the php package madmatt/id3global-service. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download madmatt/id3global-service
More information about madmatt/id3global-service
Files in madmatt/id3global-service
Package id3global-service
Short Description Allows a PHP-powered website to communicate with the GBG ID3global API to verify identities. This library is not affiliated with GBG PLC in any way.
License BSD-3-Clause
Homepage https://github.com/madmatt/id3global-service/
Informations about the package id3global-service
id3global-service
Allows a PHP-powered website to communicate with the GBG ID3global API to verify identities.
Installation
If you're not already using Composer for dependency management, please consider doing so. If you'd prefer not to, you can download the latest release from the Releases section.
Usage
The WSDL file gives an overview of the values that can be provided, these will vary by country.
Please see the Full Code Example that provides a complete overview of usage of this module.
Accessing the underlying ID3global request and response
Depending on your use case, you may need to access the underlying request sent to ID3global, or the response returned by the ID3global API. Typical use cases of this are for auditing purposes - to confirm that identity information hasn't changed since the last time an identity verification was performed for example.
In order to facilitate this, the GlobalAuthenticationService
class has a number of helper methods to give you access to the underlying data. All of the below code assumes that you have already called the ->verifyIdentity()
method and that either you have a valid BandText, or you have caught the IdentityVerificationFailureException
that may be thrown.
Debugging identity verification failures
In certain circumstances, generally when the ID3Global API produces unexpected results, you may get an IdentityVerificationFailureException
returned to you. This can happen in a number of scenarios, such as required fields being missing from the request, or data being in an invalid format.
You should also wrap your ->verifyIdentity()
calls within a try/catch to prevent users from seeing these exceptions.
By default, this library does not expose information in the exception message that would leak personally identifiable information, however this can be enabled if you are confident that the exception is properly handled (e.g. is being forwarded to a GDPR-compliant logging service). Sometimes this level of detail is necessary to determine why the API request failed.
You can enable logging of this information via the exception message with the following configuration:
All versions of id3global-service with dependencies
ext-soap Version *