Ch 26 (09/11/2019 Update): Changed the spelling of the PayerAuthConfig Endpoints by removing the letter "s"

Owned by Doug O'Bryon (Unlicensed)
Last updated: Mar 08, 2023 by Chris Bohatka
1 min read


***Changes made on 09/11/2019 are delineated below in Red.***

Update to the page: Changed the spelling of the PayerAuthConfig Endpoints by removing the letter "s"

End Points

Every endpoint takes standard SSO Request. Below is an example and description of an SSO Request.

Example of SSO Request

{
    "Signature":"rv4nqWMEETWFhYQ7FCy+/l6eoVT2XydjOXXz+BC5jqg=",
  "Timestamp":"2018-01-26T16:03:42.633Z",
    "Identifier": "MerchantRegistration-Partner-Identifier",
    "Algorithm": "SHA-256",
    "TransactionId": "07643622",
    "OrgUnitId": "55d256cfdb2b0f17304e9db8",
    "Payload": "See Endpoint for Detail"
}

Field

Description

Required

Signature

Base64 encoded SHA256 hash of timestamp, Transactiond and api key. .

Y

TimeStamp

Java Epoch time in millis (0:00:00 UTC on 1 January 1970)

Y

Identifier

api key identifier or Name value

Y

Algorithm

The hashing algorithm used to generate the Signature value. Valid options include:

  • SHA-256

Y

TransactionId

Alpha numeric value transactionId. Length 5-55 characters long

Y

OrgUnitId

Processor/Merchant level OrgUnitId, depending on the endpoint

Y

Payload

Varies with Endpoint. See EndPoint for payload description and example

Y

Merchant Endpoints

MerchantAcquirerConfig Endpoints

PayerAuthConfig Endpoints

ApiKey Endpoint