API Specifications
This documentation site has been deprecated as of September 8, 2025, and will no longer receive updates. Please refer to the new documentation site at https://docs.squadco.com.
Specification For Virtual Accounts
API KEYS (Test Environment)
Create an account on our sandbox environment: sandbox.squadco.com
Retrieve keys from the bottom of the Get Started Page
Authorization Any request made without the authorization key will fail with a 401 (Service Not Authorized) response code.
Example: Authorization: Bearer sandbox_sk_94f2b798466408ef4d19e848ee1a4d1a3e93f104046f
This API specification helps you create a virtual account and also integrates payment reconciliation for your customers.
You can also trace payments to virtual accounts and link them up with customer details.
Reconciliation: For instant settlement when using our Virtual Account, All merchant and beneficiary accounts must be GTCO Bank Accounts.
Creating Virtual Account
IMPORTANT NOTICE
Kindly share your preferred prefix with your Technical Account Manager to configure before going Live. The prefix must be a portion of your business name or an abbreviation of your business name as one word.
Customer Model
This endpoint is used to create virtual accounts for individuals/customers on your platform. Please note that there is a strict validation of the BVN against the names, Date of Birth and Phone Number. (B2C) The implication of this is that if any of the details mentioned above doesn't tally with what you have on the BVN passed, an account will not be generated. Please note that you can create virtual accounts for individuals regardless of the type of bank you provided during KYC.
Creating Virtual Accounts for Customers
POST https://sandbox-api-d.squadco.com/virtual-account
*Asterisks are required and mandatory.
Request Body
first_name*
String
customer first name
mobile_num*
String
08012345678 (doesn't take more than 11 digits)
dob*
Date
mm/dd/yyyy
last_name*
String
customer last name
gender*
String
"1" - Male, "2" -Female
address*
String
customer address
customer_identifier*
String
unique customer identifier as given by merchant
middle_name
String
customer middle name
String
customer email
bvn*
String
BVN is compulsory
beneficiary_account*
String
Beneficiary Account is the 10 Digit Bank Account Number (GTBank) provided by the Merchant where money sent to this Virtual account is paid into.
Sample Request
Sample Response
{ "status": 401, "success": false, "message": "Merchant has been restricted, please contact Habaripay support", "data": {} }
Business Model
This API allows you to create virtual accounts for your customers who are businesses and not individuals. That is, these customers are actually businesses (B2B) or other merchants. Please note that due to CBN's Guidelines on validation before account creation as well as other related Fraud concerns, you are required to request for profiling before you can have access to create accounts for businesses. Once profiled, you can go ahead and keep creating accounts for your businesses. Please note that to create virtual accounts for BUSINESSES, your KYC account needs to be a GTB account number and is mapped to the BVN provided. This doesn't apply if you are creating for individuals.
Sample Request
Creating Virtual Accounts for businesses
POST https://sandbox-api-d.squadco.com/virtual-account/business
Request Body
bvn*
String
Bank Verification Number
business_name*
String
Name of Business/Customer
customer_identifier*
String
An alphanumeric string used to identify a customer/business in your system which will be tied to the virtual account being created
mobile_num*
String
Customer's Phone Number Sample: 08012345678 (doesn't take more than 11 digits)
beneficiary_account*
String
Beneficiary Account is your 10 Digit Bank Account Number (GTBank) where money sent to this Virtual account is paid into.
Transaction Notification Service
Upon registration and verification as a merchant, you are to create a Webhook and add on your Squad Dashboard to receive notification on payments.
WEBHOOK: If a webhook is not provided, notifications won't be sent.
KINDLY ENSURE YOU HAVE A TRANSACTION REFERENCE CHECKER WHEN IMPLEMENTING WEBHOOKS TO AVOID GIVING DOUBLE VALUE ON TRANSACTIONS.
Webhook Validation
Method 1 (Hash Comparison)
The webhook notification sent carries the x-squad-signature in the header. The hash value (x-squad-signature) is an HMAC SHA512 signature of the webhook payload signed using your secret key. You are expected to create a hash and compare the value of the hash created with the hash sent in the header of the POST request sent to your webhook URL. To create the hash, you use the entire payload sent via the webhook.
Sample Implementations
Sample Webhook Notification
Note: You are expected to send us a response confirming receipt of the request
WEBHOOK VALIDATION V2
The Webhook Version 2 (V2) is an upgrade to the existing version. It follows the same structure with 2 critical updates
The addition of a new field (Version Number)
The Method of Hash Validation: Unlike previous versions, which required the hashing of the entire payload, the webhook v2 only requires the hashing of six (6) fields, each separated by a pipe (|). The values to be hashed are:
WEBHOOK VALIDATION V3
The Webhook Version 3 (V3) is an upgrade to the existing version. It follows the same structure with 3 critical updates
The Transaction Ref follows a different format (N.b. Re-queries were necessary, are to be done with the previous format)
The addition of a new field (Version Number)
The Method of Hash Validation: Unlike previous versions, which required the hashing of the entire payload, the webhook v3 only requires the hashing of six (6) fields, each separated by a pipe (|). The values to be hashed are:
Sample pipe (JavaScript)
The webhook notification sent carries the x-squad-signature in the header. The hash value (x-squad-signature) is an HMAC SHA512 signature of the webhook payload signed using your secret key. You are expected to create a hash and compare the value of the hash created with the hash sent in the header of the POST request sent to your webhook URL.
Sample Webhook V2 & V3 Notification
Sample Implementations
WEBHOOK ERROR LOG
This API allows you to retrieve all your missed webhook transactions and use it to update your record without manual input.
The top 100 missed webhooks will always be returned by default and it
This flow involves integration of two(2) APIs
Once you have updated the record of a particular transaction, you are expected to use the second API to delete the record from the error log. If this is not done, the transaction will continuously be returned to you in the first 100 transactions until you delete it.
This will only work for those who respond correctly to our webhook calls.
Also, ensure you have a transaction duplicate checker to ensure you don't update a record twice or update a record you have updated using the webhook or the transaction API.
Authorization Any request made without the authorization key (secret key) will fail with a 401 (Unauthorized) response code.
Example: Authorization: Bearer sandbox_sk_94f2b798466408ef4d19e848ee1a4d1a3e93f104046f
Get Webhook Error Log
This API returns an array of transactions from the webhook error log
GET https://sandbox-api-d.squadco.com/virtual-account/webhook/logs
Query Parameters
page
Integer
The page you are on
perPage
Integer
Number of records you want to appear on a page
Delete Webhook Error Log
This API enables you delete a processed transaction from the webhook error log
DELETE https://sandbox-api-d.squadco.com/virtual-account/webhook/logs/:transaction_ref
When you delete the transaction from the log, it won't be returned to you again. Failure to delete a transaction will result in the transaction being returned to you in the top 100 transactions returned each time you retry.
Path Parameters
transaction_ref*
String
Unique Transaction Ref that identifies each virtual account and gotten from the retrieved webhook error log
Query Customer Transaction by Customer Identifier
This is an endpoint to query the transactions a customer has made. This is done using the customer's identifier which was passed when creating the virtual account.
Query Customer Transactions
GET https://sandbox-api-d.squadco.com/virtual-account/customer/transactions/{{customer_identifier}}
Note: The customer identifier is to be passed via the endpoint being queried. That is: replace {{customer_identifier}} on the end point with the customer identifier of the customer whose transactions you want to query.
Path Parameters
customer_identifier
String
Unique Customer Identifier that identifies each virtual account
Response expected from the API to show queried Virtual Accounts.
{ "status": 400, "success": false, "message": "Customer identifier or merchant identifier is required", "data": {} }
{ "status": 401, "success": false, "message": "Merchant has been restricted, please contact Habaripay support", "data": {} }
Query All Merchant's Transactions
This is an endpoint to query all the merchant transactions over a period of time.
Query All Transactions
GET https://sandbox-api-d.squadco.com/virtual-account/merchant/transactions
Note: The endpoint is to be queried using just the authorization key from the dashboard
{ "status": 400, "success": false, "message": "Merchant identifier is required", "data": {} }
{ "status": 401, "success": false, "message": "Merchant has been restricted, please contact Habaripay support", "data": {} }
{ "status": 404, "success": false, "message": "Merchant is not profiled for this service, please contact Habaripay support", "data": {} }
Query Single Transaction Using Transaction Ref
This endpoint allows you to query a single transaction using the system-generated transaction reference, which can be obtained from the webhook notification or dashboard.
The Ref to be inputted should be your unique ref
Query Parameters
transactionReference
String
Unique Identifier of a transaction
Get Customer Details by Virtual Account Number
This is an endpoint to retrieve the details of a customer using the Virtual Account Number
Retrieve Virtual Account Details
GET https://sandbox-api-d.squadco.com/virtual-account/customer/{{virtual_account_number}}
Note: The virtual account number is to be passed via the endpoint being queried. That is: replace {{virtual_account_number}} on the end point with the virtual account number whose details you want to retrieve.
Path Parameters
virtual_account_number*
String
Unique 10-digit virtual account number assigned to a customer
Get Customer Details Using Customer Identifier
This is an endpoint to retrieve the details of a customer'svirtual account using the Customer Identifier
Retrieve Virtual Account Details
GET https://sandbox-api-d.squadco.com/virtual-account/{{customer_identifier}}
Note: The customer_identifier is to be passed via the endpoint being queried. That is: replace {{customer_identifier}} on the end point with the customer identifier of the customer whose virtual account you want to retrieve.
Path Parameters
customer_identifier
String
Unique Customer Identifier that identifies each virtual account
Query All Merchant's Virtual Accounts
This is an endpoint to look-up the virtual account numbers related to a merchant.
Find All Virtual Account Number by Merchant
GET https://sandbox-api-d.squadco.com/virtual-account/merchant/accounts
This is an endpoint for merchants to query and retrieve all their virtual account.
Query Parameters
page
String
Number of Pages
perPage
String
Number of Accounts to be returned per page
startDate
Date
YY-MM-DD
EndDate
Date
YY-MM-DD
Update Beneficiary Account
Sample Request
This is used to update beneficiary account
PATCH https://sandbox-api-d.squadco.com/virtual-account/update/beneficiary/account
Request Body
beneficiary_account*
String
10 digit valid NUBAN account number
virtual_account_number*
String
The Virtual account number whose beneficiary account is to be updated
Simulate Payment
This is an endpoint to simulate payments
Simulate Payment
POST https://sandbox-api-d.squadco.com/virtual-account/simulate/payment
This is an endpoint to simulate payment
*asterisks are required and mandatory.
Headers
content-type*
application/json
Authorization*
String
Private Key or Secret Key (Gotten from your dashboard)
Request Body
virtual_account_number*
String
Virtual Account number of customer that wants to make payment.
amount
String
Simulated Amount
Go Live
To go live, simply:
1. Change the base URL for your endpoints from sandbox-api-d.squadco.com to api-d.squadco.com
2. Sign up on our Live Environment
3. Complete your KYC
4. Share the Merchant ID with the Technical Account Manager for Profiling
5. Use the secret keys provided on the dashboard to authenticate your live transactions
Last updated