Local Bank Cards

Local bank cards managed by Numo network

Pay

Pay the transaction.

Confirm (Pay)

POST https://api.plutus.ly/api/v1/transaction/localbankcards/confirm

Pay the transaction

Headers

NameTypeDescription

Authorization*

String

Bearer: [Access token]

X-API-KEY*

String

API Key

Request Body

NameTypeDescription

amount*

String

Transaction amount in Libyan dinars.

Formatting is allowed with a maximum of two decimal places: XXX, XX.X, XX.XX

invoice_no*

String

Invoice number associated with transaction, must be unique and not previously used.

return_url*

String

Redirect URL after completing the payments

customer_ip

String

[Optional] Customer IP address

lang

String

[Optional] Accepts ar or en, by default ar

{
    "status": 200,
    "result": {
        "code": "CHECKOUT_REDIRECT",
        "redirect_url": "https://xxxxxxxxxxxxxxx"
    }
}
curl --location --request POST 'https://api.plutus.ly/api/v1/transaction/localbankcards/confirm' \
--header 'X-API-KEY: [API_KEY]' \
--header 'Authorization: Bearer [ACCESS_TOKEN]' \
--form 'amount="[AMONUT]"' \
--form 'invoice_no="[INVOICE_NO]"' \
--form 'return_url="[RETURN_URL]"' \
--form 'customer_ip="[CUSTOMER_IP]"'

Callback handler

The callback will be received from Plutu when the transaction is completed or canceled. This gives a Merchant better control of how the transaction is processed on the Merchant's side. This is useful e.g. when you want to mark an order as paid, update your shop's inventory, or add appropriate records to Merchant’s internal accounting system.

Callback response parameters:

The callback is called with HTTP GET and with the same query string parameters as in the redirect

ParameterDescription

gateway

Gateway name: localbankcards

approved

It will only be returned if the transaction is approved and completed, and must be checked to be 1 (true)

canceled

It will only be returned if the transaction is canceled by the customer

invoice_no

Invoice number sent in the pay request

amount

amount sent in the request

transaction_id

Plutu transaction id

hashed

Hash message authorization code (HMAC) is used to verify both the data integrity and the authorization of a message.

SHA-256 HMAC is calculated as follows:

  • The SHA-256 HMAC calculation includes all response query string parameters and key-value pairs except the “hashed” parameter.

  • Create an SHA-256 HMAC of the resultant string using the secret key created in the Plutu account, convert it to uppercase, and compare it with the “hashed” parameter received in the callback.

Last updated