/home/kueuepay/public_html/vendor/stella-maris/clock/README.md
# Clock

An implementation of the proposed PSR-20 clock-interface

[![Total Downloads](http://poser.pugx.org/stella-maris/clock/downloads)](https://packagist.org/packages/stella-maris/clock)
[![Latest Stable Version](http://poser.pugx.org/stella-maris/clock/v)](https://packagist.org/packages/stella-maris/clock)
[![Latest Unstable Version](http://poser.pugx.org/stella-maris/clock/v/unstable)](https://packagist.org/packages/stella-maris/clock)

[![pipeline status](https://gitlab.com/stella-maris/clock/badges/main/pipeline.svg)](https://gitlab.com/stella-maris/clock/-/commits/main)

## Installation

```bash
composer require stella-maris/clock
```

## Usage

This interface allows one to inject one of the implemntations that provide the 
clock-interface.

```php
use StellaMaris/Clock/CLockInterface;

final class PastChecker
{
    public function __construct(private ClockInterface $clock) {}
    
    public function hasDateTimeAlreadyPassed(DateTimeImmutable $item): bool
    {
        return $item < $this->clock->now();
    }
}
```

## Why

Within the Framework Interoperability Group (FIG) a working group has started in 2021 to
create a ClockInterface. The works on that have been rather fast and already in the mid of 
2021 the interface was more or less finally decided upon. 

### So why this Interface?

Since mid 2021 no further work has been happening on the Working Group. All requests towards
the editor and the sponsor weren't met with any reaction.

So after a lot of discussions on the official working group channel I decided to bring this 
interface forward by providing the currently agreed upon interface as a separate package 
on packagist.

### But what when the PSR Interface is provided?

There are two possibilities: 
* Either the interface will be provided by the FIG as it is currently,
then this interface will extend the PSR-20 one so that all implementations of this 
interface will be immediately PSR20 compatible. 
* Or the PSR20 interface will look different: Then all current implementations will
need to provide a spearate implementation for PSR20 compatibility and this interface will 
simply coexist with the PSR20 one.

## Documentation

For a more thorough information about the interface please check the PSR-20 documentation 
at https://github.com/php-fig/fig-standards/blob/master/proposed/clock.md and 
https://github.com/php-fig/fig-standards/blob/master/proposed/clock-meta.md

Access Token

Get Access Token

Get access token to initiates payment transaction.

Endpoint: POST generate-token
Parameter Type Comments
client_id string Enter merchant API client/primary key
secret_id string Enter merchant API secret key
env string Enter merchant API environment
merchant_id string Enter merchant API merchant id
Just request to that endpoint with all parameter listed below:
                    
                        Request Example (guzzle)
                        

<?php
require_once('vendor/autoload.php');
$client = new \GuzzleHttp\Client();
$response = $client->request('POST', $base_url. 'v1/generate-token', [
'headers' => [
  'accept' => 'application/json',
  'content-type' => 'application/json',
 ],
'form_params' => [
  'client_id' => '$client_id',
  'secret_id' => 'secret_id',
  'env' => 'env',
  'merchant_id' => 'merchant_id',
 ],
]);
echo $response->getBody();
                    
                        
**Response: SUCCESS (200 OK)**
{
 "message": {
 "success": [
  "Successfully token is generated"
 ]
},
"data": {
 "token":"eyJpdiI6InpkczhjTjhQdVhUL2lKQ0pSUUx6aUE9P
SIsInZhbHVlIjoiVGVBTVBDTXltbjNZcEIvdEJveGpTSno3TU5NRUtn
VkhCZ1pHTFNCUnZGQ2UxMnYxN202cEE1YVRDTEFsc0ZERExoTjdtL0dTL2x
oU3QzeUJJOExiMUx5T0w1L0llUXhTUkU1cWVLWEdEbEplb0dKNXcwbTNRM0
VxdkUwYzZuNFdtNkhMQ0pRZysyNWkvdzBxSlBoSVBSOGFTekNnR2RXNHVtc
G9lMGZOTmNCcm1hR3c5Sk9KTnB4Y3ltZDl6cm90MThrR21Ca3B1azc3bXRi
Q0J6SW96UVo1elNkU1ZqeE05bTcwWGp1MEUxWlJFdnNWTmpSbnVpeW92b2U
4dXZkUGgyb1VmK0luaGdyaFlsVTZlcVpVRnZlTG1DeFF6Ykk2T2h6Z3Jzbn
IyNHpNdHowSE5JdDR0Y0pZT20zUm1XYW8iLCJtYWMiOiJlY2M4NGE1OGUzYz
kzYzk0YzljNmVmNjE0YWI0ZDIwOGI3NDQ2YWEyY2ZhNzc0NzE4ZmY1ZmYyMz
IyZmQzNDY1IiwidGFnIjoiIn0=",
},
"type": "success"
}
                    
                        
**Response: ERROR (400 FAILED)**
{
 "message": {
 "error": [
  "Invalid credentials."
 ]
},
"data": null,
"type": "error"
}