POST
/
make_payment
{
  "response_message": "<string>",
  "response_code": "<string>",
  "redirect_url": "<string>"
}

Authorization

Authorization
string
required
Basic authentication header of the form Basic <encoded-value>, where <encoded-value> is the base64-encoded string username:password.

Request Body

service_id
integer
required
Your unique service identifier. You’ll receive this when you register your service with us.
reference
string
required
Your internal reference for this payment.
transaction_id
string
required
A unique identifier for this transaction. Ensure this is unique for each request to avoid duplicate transactions. Use this to track the transaction in your system.
trans_type
string
required
The type of transaction. Use ‘DTTW’ for Deposit to Transfer Wallet.
amount
number
required
The amount to be transacted. Use a decimal point for fractional amounts (e.g., 10.50).
nw
string
required
The network provider for mobile money transactions. Use ‘MTN’ for MTN Mobile Money, ‘TEL’ for Telecel Cash, ‘AIR’ for AirtelTigo Cash, or ‘CRD’ for card payments.
nickname
string
required
You can use your service name or the purpose of the transaction as the nickname as this will be shown on the payers phone when they receive the payment request.
payment_option
string
required
The payment method. Use ‘MOM’ for mobile money, ‘CRD’ for card payments, or ‘CRM’ for both card and mobile money.
currency_code
string
required
The currency code for the transaction. For example, use ‘GHS’ for Ghanaian Cedi, ‘USD’ for US Dollars.
currency_val
string
required
The currency value. This is typically the amount in the currency specified in the currency_code unless you’re dealing with a specific exchange rate scenario.
callback_url
string
required
Your URL where we’ll send transaction status updates. Ensure this endpoint is set up to receive POST requests.
landing_page
string
required
Your landing page after the transaction has been completed.
request_time
string
required
The timestamp of your request. Use the format YYYY-MM-DD HH:MM (e.g., ‘2024-06-28 12:46’).

Response

response_message
string
A human-readable message describing the result of the payment initiation.
response_code
string
A code indicating the status of the payment initiation. Refer to our response code documentation for details.
redirect_url
string
The payment page to redirect your app or users to for the actual payment.

Example Request

curl -X POST https://api.thebridgesolutions.com/make_payment \
  -H "Authorization: Basic YOUR_ENCODED_CREDENTIALS" \
  -H "Content-Type: application/json" \
  -d '{
    "service_id": 12345,
    "reference": "REF123456",
    "transaction_id": "TXN987654",
    "trans_type": "DTTW",
    "amount": 100.50,
    "nw": "CRD",
    "nickname": "Wallet Funding",
    "payment_option": "CRD",
    "currency_code": "GHS",
    "currency_val": "100.50",
    "callback_url": "https://your-domain.com/callback",
    "landing_page": "https://your-domain.com/landing",
    "request_time": "2024-06-28 12:46"
  }'

Example Response

// MOBILE MONEY
{
  "response_message": "Request successfully received for processing",
  "response_code": "202",
}
// CARD PAYMENT
{
  "response_message": "Successful",
  "response_code": "000",
  "redirect_url": "https://paymentpage.com/en/payment/123456789"
}