​
Overview

Monieswitch provides an easy way to check transfer charges before making a transfer. This guide explains how to view transfer charges using our system.

​
How Transfer Charges Work

Transfer charges are fees associated with transferring funds from one account to another. These charges can be incurred by the sender, the recipient, or a subaccount.

​
Fee Bearer Options

When making a transfer, you can specify who bears the transfer charges. The fee bearer determines who will be responsible for any associated charges:
  • customer: The end user making the payment bears the charges
  • account: You bear the charges
  • subaccount: A designated subaccount bears the charges
Note: If selecting subaccount, you’ll need to choose from your existing subaccounts.

​
Get Transfer Charges

​
API Endpoint

GET https://nini.monieswitch.com/payout/charges

​
Authentication

Authentication is required using an access token in the request header: 
Authorization: Bearer {{merchantAPIKey}}

​
Request Parameters

ParameterTypeRequiredDescription
amountnumberYesThe amount to be transferred

​
Example Request

curl --location 'https://nini.monieswitch.com/payout/charges?amount={AMOUNT}' \
--header 'Authorization: Bearer {SECRET_KEY}'

​
Response Format

A successful request returns the following response: 
{
  "status": true,
  "data": {
    "charges": 50
  }
}

​
Response Fields

FieldTypeDescription
statusbooleanIndicates if the request was successful
data.chargesnumberThe calculated transfer charge for the amount

​
Best Practices

  1. Authentication
    • Keep your SECRET_KEY token secure
    • Never expose your SECRET_KEY token in client-side code
  2. Error Handling
    • Implement proper error handling for failed requests
    • Validate the amount parameter before making the request
  3. Testing
    • Test the endpoint with various amount values
    • Verify the response format and charges calculation

​
Rate Limits and Usage

Please be aware of the following usage guidelines:
  • The API has rate limits in place
  • Excessive requests may be throttled
  • Cache the results when appropriate

API

Refer to our API Documentation for integration details