Seerbit Release Notes
4 months ago
Personalised Checkout - V2

With our new and updated personalised checkout, you can now tailor your checkout page, from a generic page to a customized page. Your customers will remain within the ecosystem of your brand even during the payment process.


You can also control the look and feel of your your checkout in a few clicks:

  • Navigate to your settings
  • Select checkout customisation 
  • Set your preferred brand color from your dashboard and proceed as seen below.







5 months ago
Mobile Money, Wallet Payment Options - V2

Mobile money is a new payment option by SeerBit. In addition to our card, bank account, transfer and USSD payment options, merchants can now accept payments from M-Pesa, MTN, Vodafone, Airtel, Airtel Tigo, Equitel, Orange money, MooV, YUP, Mobicash, E-Money and Wizall mobile money users in Ghana, Kenya, Uganda, Malawi, Rwanda, Senegal, Cote d’Ivoire, Cameroon, Burkina Faso, and Mali.


View documentation here: Mobile Money, Wallets

7 months ago
Webhooks and Events - v2

With the new and updated version, your Webhook responses have now been extended to provide more data, event types, and queue intervals. This further makes communication via your APIs and services extensible and flexible.


Our event types now include


  • refund
  • dispute
  • transaction
  • transaction.recurrent
  • transaction.wallet
  • transaction.recurring.debit


View documentation here: Webhook & Events

7 months ago
Transaction status endpoint extended properties - V2

When retrieving a transaction status, SeerBit’s response is a lot more detailed and insightful. The request payload remains the same, but the response has now been extended to include a range of data sets ranging from payment types, product description (if applicable), and gatewayMessage.


A simple payload can be seen below:

        "payments": {
            "redirectLink": "https://checkout.seerbitapi.com",
            "amount": "100.00",
            "email": "johndoe@gmail.com",
            "mobilenumber": "08033456599",
            "publicKey": "merchant public key",
            "paymentType": "CARD",
            "productId": "Foods",
            "productDescription": "RASPBERRY",
            "maskedPan": "5123-45xx-xxxx-0008",
            "gatewayMessage": " APPROVED",
            "gatewayCode": "00",
            "gatewayref": "F602334371587044536564",
            "mode": "test",
            "callbackurl": "https://checkout.seerbitapi.com",
            "redirecturl": "https://checkout.seerbitapi.com",
            "channelType": "Mastercard",
            "sourceIP": "127.0.0.1:3456",
            "deviceType": "Apple Laptop",
            "cardBin": "512345",
            "lastFourDigits": "0008",
            "type": "3DSECURE",
            "country": "NG",
            "currency": "NGN",
            "paymentReference": "2FURTHERTEST1235678129",
            "processorCode": "00",
            "processorMessage": "Successful",
            "reason": "Successful"
        }

10 months ago
Callback URL introduced for inline script V1

We understand how important it is for your customers to be redirected to a customised page where you can display a transaction receipt on your application after every transaction, so we have included a callback URL field in the payload when using our inline script.


Alternatively, If you provide a callback URL, we will redirect you back to the URL after every transaction.


Kindly ensure you confirm the status of the transaction by calling our status confirmation endpoint using the reference sent back as query string parameter in the URL. See guide Here


Here’s a sample of a callback URL after redirection with query string parameters:


https://merchanturl.com?linkingreference=F641426531573992889243&code=00&message=Successful&reference=IHrE1573992870916


Here’s a sample of the payload:


{
"tranref": "Pg5" + new Date().getTime(), 
"currency": "NGN"
"description": "test",
"country": "NG",
"amount": "1.00",
"clientappcode": "app1", 
"callbackurl": "http://youdomain.com", 
"public_key": "tNUFstIHrE",
"product_id": "my unique id", 
"full_name": "test test",
"email": "test@emaildomain.com",
"mobile_no": "08011111111",
}


Please, take note of these guides:


  • You have to ensure that the callback URL is available on the WWW and not localhost, as we cannot redirect to localhost.
  • Ensure your URL doesn’t require some form of authentication, else, your customer won’t be redirected to the intended page.
a year ago
Improved transaction details

Hello there, 


We have introduced an alternative way of referencing your transactions. We added an alternative transaction/product reference field for unique transaction identification. You can now send your ISBN, SKU or any other unique reference for your product or service as an alternative reference when initialising a transaction.

This field is named productId and should be sent in every request payload for each transaction.


See example payload below:

{
"publicKey":"cqjphzlAEl", //replace this with your own public key
"amount":"10000.00",
"currency":"NGN",
"country":"NG",
"paymentReference":"5fgj77tx867563777",
"email":"test@yourdomain.com",
"productId":"Unique product id",
"productDescription":"Product description",
"callbackUrl":"http://yourdomain.com",
"hash":"3af7fbd7de08cad92c83e178c827cc7e0",
"hashType":"sha256"
}


The new field will be displayed on each transaction on your dashboard as Product ID. You can also search for transactions using this field.



a year ago
Seerbit V1.0.1 release


We have released a new version that introduces some new upgrades to enhance integration experience. With the new updates, You can now: 


1. Initialise a transaction via API call using our standard checkout option. Please see the full documentation Here


2. Verify a transaction status before giving value to your customers. : All that is required is the transaction reference to be added as a parameter in a GET request. 

https://staging.seerbitapigateway.com/sbt/api/card/v1/get/transaction/status/{transaction-reference}

3. Bearer token would no longer be required for authentication. However, an AES encrypted private key value is now required to be sent in Header requests.

      4. Request payload for checkout standard has to be hashed using SHA256 algorithm.

      5. Transaction request and response payload has been modified slightly to accommodate more fields to strengthen transaction security and add more details to each transaction.

      {
      "publicKey":"cqjphzlAEl",
      "amount":"100",
      "currency":"NGN",
      "country":"NG",
      "paymentReference":"5fgj77tx867563777",
      "email":"customer-email@email-server.com",
      "productId":"lbs200978ng",
      "productDescription":"Laced Brown Shoe",
      "callbackUrl":"http://www.yourwebsite.com/callback-path",
      "hash":"3af7fbd7de08cad92c83e178c827cc7e06198279691e",
      "hashType":"sha256"
      }

      As stated above, productId, hash, and hashType has been added as a field for each transaction request.


      Webhook response payload has been updated with new data

      {
      "name":"John Doe",
      "amount":"100.00",
      "mobile":"09060007388",
      "reference":"x30",
      "status":"APPROVED",
      "generatedAt":"2019:08:06 10:28:12",
      "hashvalue":"08hgtt657fgvhvhjgj9708ho_+89uhk khvjv"
      }

      We've also updated the response payload of the success callback function

      {
      "status": "SUCCESS",
      "data": {
      "code": "00",
      "payments": {
      "reference": "lAEl1569141936732",
      "linkingreference": ?F132338911569141957013?,
      "callbackurl": "https://checkout.seerbit.com"
      },
      "message": "Approved by Financial Institution"
      }
      }

      a year ago
      We've got Release Notes

      Learn more and do more with our product updates


      We're excited to let you know that we have started publishing our product updates in a public channel so you're always up-to-date.

      Keep an eye on this page for new features, improvements and bug fixes that are made on our SeerBit applications and services.