third-party-prc-api icon

third-party-prc-api

(0 reviews)

home

Third Party Process API

Base URLS:

Description:

Process APIs do the business transformations and are responsible for sending or receiving data through System APIs. The Third Party Process API communicates with T24 / QBank / Creditlens / Loyalty System API. Mulesoft exposes the REST endpoints for the following operations :

  1. Get Customer Cash Flows
  2. Get Customer Rating
  3. Get Financial Statement
  4. Loyalty Redeem Points
  5. Loyalty Gain Points
  6. Loyalty Submit Cash Back
  7. Get Court Cases
  8. Print Customer Court Cases
  9. Loyalty Get Profile
  10. Loyalty Get Steps Info
  11. Loyalty Get Transaction History
  12. Loyalty Calculate Amount
  13. CI Confirm Capital Invest Accounts Link Request
  14. CI Get Capital Invest Accounts
  15. CI Get Capital Invest Accounts Transactions
  16. CI Remove Capital Invest Accounts Link
  17. CI Request Capital Invest Accounts Link
  18. Submit Customer Data IBAN to SSC
  19. Western Union - Get State List
  20. Western Union- Get Delivery Services
  21. Western Union - Transaction Inquiry
  22. Western Union - Refund Search
  23. Western Union - Refund Store
  24. Western Union - Get DeliveryOptionTemplate

Technical Specifications

Headers

Below are the mandatory/optional headers that are set with every HTTP Request from Mule API towards Creditlens.

HeaderNameSample ValueOptional?
client_id9712801dbaaffg90d43a0b09c59fdaf21e65524235436Mandatory
client_secret234d8AeC33e34bE1b3eiud31b2887cD4Mandatory
AuthorizationBearer afdca88b-9ed0-344b-8af0-b2195e382574Optional
x-user-idIIBUserOptional
x-channel-idDEVCHLMandatory
x-sub-channel-idOptional
x-correlation-id13243564564Mandatory
x-bank-idCBOJMandatory
x-debug-flag0Optional (enum - 0 or 1)
x-customer-id2100122Optional (mandatory for customer facing channels)

Error handling

HTTP Status

The HTTP error codes are:

  • 400 - Bad Request: An error in the client request (Mostly due to validations)
  • 401 - Unauthorized: User can't be authenticated
  • 403 - Forbidden: The server cannot give access to the resource
  • 404 - Not Found: The resource defined in the URL doesn't exist
  • 405 - Method Not Allowed
  • 406 - Not Acceptable
  • 415 - Unsupported Media Type
  • 500 - Internal Server Error: The server encountered an unexpected condition
  • 501 - Not Implemented

Error Response

A REST API should reply with an error code and a message to be shown to the consumer.

{
    "status": {
        "success": false,
        "code": "400",
        "reasonCode": "BadRequest",
        "arabicMessage": "",
        "englishMessage": "No records were found that matched the selection criteria",
        "errorCode": "",
        "backendErrorMessage": ""
    }
}

Below fields should be given back to Channel if x-debug flag = 1

    "errorCode": "",
    "backendErrorMessage": "",

Api Security

Below polices are applied.

NameDescriptionExample
Client ID EnforcementIt restricts access to a protected resourceclient_id: 9d41a8940c5e4181aace6fc5e6cfffc3 client_secret: aB9D5Bd7450d49F584F23250D96872fD
IP Allowlistallows a list or range of IP addresses to access and interacts with a configured API endpoint.192.168.61.1
192.168.61.2
192.168.62.1

Reviews