Contents x
    Successful HTTP Payment Push Notification
    • 10 Oct 2023
    • 1 Minute to read
    • Contributors
    • Print
    • Dark
      Light
    • PDF
    Contents

    Successful HTTP Payment Push Notification

    • Updated on 10 Oct 2023
    • 1 Minute to read
    • Contributors
    • Print
    • Dark
      Light
    • PDF
    Article summary

    This callback notification will update the Merchant once a successful payment is conducted for each created invoice. The notification will be initiated from SmartLink to the Merchant, as there will be no need for the merchant to issue any request to receive this notification, only setting up the interface which will receive this notification. This message is sent as an HTTP Request containing the below parameters. 

    Output Parameters

    ParameterDescription
    Response.MerchantID
    required 

    Alphanumeric value representing the merchant Id.

    • Field Type: Alphanumeric
    • Length: 40
    • Sample Data: maisMerchant

    Response.InvoiceId
    required 

     Alphanumeric value representing the Invoice ID.

    • Field Type: Alphanumeric
    • Length: 60
    • Sample Data: 56534333
    Response.InvoiceStatus
    required 

    Alphanumeric value representing the invoices Status which will ALWAYS be PAID.

    • Field Type: Alphanumeric
    • Length: 10
    • Sample Data: PAID
    Response.Amount
    required

    A numeric value represents the invoice amount determined by the merchant upon invoice creation. It will be  ISO formatted with no decimal point.

    • Field Type: Numeric
    • Length: 9
    • Sample Data: 100
    Response.CurrencyISOCode
    required     		The numeric ISO Code of the currency for the invoice upon invoice creation.

    • Field Type: Numeric
    • Length: 3
    • Sample Data: 400
    Response.RRN
    optional    		The Reference Retrieval Number of the payment.

    • Field Type: Alphanumeric
    • Length: 50
    • Sample Data: 201608161029435230000000000
    Response.ApprovalCode
    optional    		The Approval code for the payment.

    • Field Type: Alphanumeric
    • Length: 10
    • Sample Data: 0000125480
    Response.MaskedCardNumber
    optional    		Alphanumeric value representing the masked card number.

    • Field Type: Alphanumeric
    • Length: 20
    • Sample Data: 401200******3335
    Response.CardType
    optional

    Alphanumeric value represents the card type used during the payment.


    • Field Type: Alphanumeric
    • Length: 20
    • Sample Data: Visa
    Response.AuthorizedAmount
    conditional    		A numeric value represents the actual amount used in the payment. It will be ISO formatted with no decimal point.


    • Field Type: Numeric
    • Length: 9
    • Sample Data: 100
    Condition:
    This parameter will be provided back to the merchant if the MCP is enabled for this merchant.
    Response.AuthorizedCurrencyISOCode
    conditional

    The numeric ISO Code of the actual currency used in the payment.

    • Field Type: Numeric
    • Length: 3
    • Sample Data: 840
    Condition:
    This parameter will be provided back to the merchant if the MCP is enabled for this merchant.
    Response.Token
    conditional

    This value will be part of the response if the invoice was created with a flag to generate a token.

    This parameter is a part of the tokenization. For more information, see Tokenization.

    • Field Type: Alphanumeric
    • Length: 64
    • Sample Data: 17b61316feafe09feb806ce33cdbfc85aed1b4173ed604f8fd5fa3cf72a02e27


    HTTP Authentication Parameters

    The below parameters will be included within the HTTP authorization request header as a basic authentication.

    ParameterDescription
    username
    optional

    An Alphanumeric value representing the username Provided by the merchant.

    • Field Type: Alphanumeric
    • Length: 255
    • Sample Data: user123
    password
    optional

    An Alphanumeric value passwrod provided by the merchant.

    • Field Type: Alphanumeric
    • Length: 255
    • Sample Data: P@ssword


    What's Next