Praxis Wiki logo

Payment API |DepositCapture Recommended


DepositCapture API function lets you capture the authorized payment card deposit transaction. In simple words it is an API call to send the authorized customer's funds to the merchant account immediately.
Authorize and following Capture/Cancel API methods can be used by the merchant for automated capture or cancel operations upon the authorized transaction notification (earlier integrations - AuthorizedDeposit)

{danger.fa-exclamation} IMPORTANT #1: This notification is only specific to payment card processors that support authorization and capture as two separate steps (the standard approach is a combined sale action).


{danger.fa-exclamation} IMPORTANT #2: Even if the PSP supports the authorize and capture steps, you should contact the Praxis support representative to confirm that the two-step processing is enabled for your channel within Praxis Backoffice.

ENDPOINTS

Name URL
Sandbox https://gateway-test.praxispay.com/api/deposit-capture
Live https://gateway.praxispay.com/api/deposit-capture

REQUEST PARAMETERS

Variable Type Description
merchant_id varchar(50) Required. Merchant API client account identifier
frontend varchar(50) Required. Cashier FrontEnd name, normally it is a common name of the website. Linked to a specific base currency.
trace_id int(11) Required. Transaction identifier at Praxis that is previously sent to CRM within AuthorizedDeposit notification.
timestamp int(11) Required. Request time. URL will be active during 1 min after this time
version varchar(3) Required. API version
signature varchar(96) Required. Hash of the request parameters

RESPONSE PARAMETERS

Variable Type Description
status int Required.
- 0 if the request was successful
- Negative integer if internal server/network error occurs
- Positive integer if application/logical error occurs
description varchar(256) Required. Accurate description of the result. Return the actual error for any exception as it helps to diagnose issues in production
version varchar(3) Required. API version
signature varchar(96) Required. sha384 HASH code of response (same as in request)

EXAMPLE

Request

For example below: Merchant Secret = "MerchantSecretKey"

curl -X POST \
  https://gateway.praxispay.com/api/deposit-capture \
  -H 'Content-Type: application/json' \
  -H 'cache-control: no-cache' \
  -d '{
    "frontend":"Integration TEST USD",
    "merchant_id":"Test-Integration-Merchant",
    "timestamp":1559825373,
    "trace_id":"752856",
    "version":"1.1",
    "signature":"c1eb4464bce78dd099501fbdbc6c9b9979070b4d82ef47fbbfbf9535104934d4abd77bfd9480685b317d60db5339097b"
}'

Response (OK)

{
    "description": "Successful capture: TraceID=752856",
    "status": 0,
    "version": "1.1",
    "signature": "79336707e133167e87bebf133bddb154847e477bc0195e19fb1a8ce9c543f6647f8e1d871d548afda3ecea8bfae92e1f"
}

Response (ERR)

{
    "description": "Capture failed. Transaction not found: TraceID=752856",
    "status": 1,
    "version": "1.1",
    "signature": "b3ecb0f626d13d4eea7c01cdef3a0e3e48d6e079d3a9e440005542c2a9a43e4588d1ce1cd0ee1d0bf93d4effb909328b"
}

Please refer to How to Build Signature for details on signing the request.

You are currently viewing version 3.1 Latest version here