Berbix PHP SDK

This Berbix PHP library provides simple interfaces to interact with the Berbix API.

PHP 7 or greater is required to use this API library.

Installation

You can install the library through Composer.

composer require berbix/berbix-php

Usage

Constructing a client

$client = new \Berbix\Client("your_api_secret_here");

Create a transaction

$transactionTokens = $client->createTransaction(array(
  'customerUid' => "internal_customer_uid", // ID for the user in internal database
  'templateKey' => "your_template_key", // Template key for this transaction
));

Create tokens from refresh token

$refreshToken = ''; // fetched from database
$transactionTokens = \Berbix\Tokens::fromRefresh($refreshToken);

Fetch transaction data

$transactionData = $client->fetchTransaction($transactionTokens);

Reference

Client

Methods

constructor(string $apiSecret, array $opts)

Supported options:

• apiHost - An optional custom host (used for development purposes).
• httpClient - An optional override for the default PHP HTTP client.

createTransaction(array $options): Tokens

Creates a transaction within Berbix to initialize the client SDK. Typically after creating a transaction, you will want to store the refresh token in your database associated with the currently active user session.

Supported options:

• email - Previously verified email address for a user.
• phone - Previously verified phone number for a user.
• customerUid - An ID or identifier for the user in your system.
• templateKey - The template key for this transaction.
• matchData - The array of data to compare against the extracted data
• • givenName - given name to match against
• • familyName - family name to match against
• • middleName - middle name to match against
• • dateOfBirth - date of birth to match against
• • idExpiryDate - id expiry date to match against

createHostedTransaction(array $options): array

Creates a hosted transaction within Berbix. Typically after creating a transaction, you will want to store the refresh token in your database associated with the currently active user session.

Supported options:

• email - Previously verified email address for a user (optional).
• phone - Previously verified phone number for a user (optional).
• customerUid - An ID or identifier for the user in your system.
• templateKey - The template key for this transaction.
• completionEmail - The email to send a notification to upon completion.
• redirectUrl - The URL to redirect the user to upon completion.
• matchData - The array of data to compare against the extracted data
• • givenName - given name to match against
• • familyName - family name to match against
• • middleName - middle name to match against
• • dateOfBirth - date of birth to match against
• • idExpiryDate - id expiry date to match against

Returns an associative array with the following values:

• tokens - The Tokens object for the transaction.
• hostedUrl - The URL for the hosted transaction.

fetchTransaction(Tokens $tokens): array

Fetches all of the information associated with the transaction. If the user has already completed the steps of the transaction, then this will include all of the elements of the transaction payload as described on the Berbix developer docs.

refreshTokens(Tokens $tokens): void

This is typically not needed to be called explicitly as it will be called by the higher-level SDK methods, but can be used to get fresh client or access tokens.

validateSignature(string secret, string body, string header): bool

This method validates that the content of the webhook has not been forged. This should be called for every endpoint that is configured to receive a webhook from Berbix.

Parameters:

• secret - This is the secret associated with that webhook. NOTE: This is distinct from the API secret and can be found on the webhook configuration page of the dashboard.
• body - The full request body from the webhook. This should take the raw request body prior to parsing.
• header - The value in the 'X-Berbix-Signature' header.

deleteTransaction(Tokens $tokens): void

Permanently deletes all submitted data associated with the transaction corresponding to the tokens provided.

updateTransaction(Tokens $tokens, array $parameters): array

Changes a transaction's "action", for example upon review in your systems. Returns the updated transaction upon success.

Parameters:

• action: string - A string describing the action taken on the transaction. Typically this will either be "accept" or "reject".
• note: string - A string containing an optional note explaining the action taken.

overrideTransaction(tokens: Tokens, parameters: object): void

Completes a previously created transaction, and overrides its return payload and flags to match the provided parameters.

Parameters:

• responsePayload: string - A string describing the payload type to return when fetching transaction metadata, e.g. "us-dl". See our testing guide for possible options.
• flags: array(string => string) - An optional list of flags to associate with the transaction (independent of the payload's contents), e.g. ["id_under_18", "id_under_21"]. See our flags documentation for a list of flags.
• overrideFields: array(string => string) - An optional mapping from a transaction field to the desired override value, e.g. 'overrideFields' => array('date_of_birth' => '2000-12-09')

Tokens

Properties

string accessToken

This is the short-lived bearer token that the backend SDK uses to identify requests associated with a given transaction. This is not typically needed when using the higher-level SDK methods.

string clientToken

This is the short-lived token that the frontend SDK uses to identify requests associated with a given transaction. After transaction creation, this will typically be sent to a frontend SDK.

string refreshToken

This is the long-lived token that allows you to create new tokens after the short-lived tokens have expired. This is typically stored in the database associated with the given user session.

number transactionId

The internal Berbix ID number associated with the transaction.

Date expiry

The time at which the access and client tokens will expire.

Static methods

fromRefresh(string $refreshToken): Tokens

Creates a tokens object from a refresh token, which can be passed to higher-level SDK methods. The SDK will handle refreshing the tokens for accessing relevant data.