Skip to main content
POST
Calculate transaction fees
This route calculates fees server-side before launching a collection or disbursement. You can identify the service with serviceId, service_id, provider, serviceCode, or service_code. For a direct API application, the fee bearer comes from the authenticated application configuration or the internal X-SP-Fee-Bearer header. For a plugin, send origin: "PLUGIN" and provide feeBearer in the payload or query string. The payload has priority. When feeBearer is CUSTOMER, payableAmount includes fees. When feeBearer is MERCHANT, merchantNetAmount indicates the merchant net amount after fees.

Authorizations

x-sp-auth-token
string
header
required

JWT Bearer emis par Mysoleas Identity Cloud. Format: Bearer <access_token>.

Query Parameters

feeBearer
enum<string>

Prioritaire seulement pour les flux plugin lorsque le payload ne fournit pas feeBearer.

Available options:
CUSTOMER,
MERCHANT

Body

application/json
amount
integer
required
Example:

10000

currency
string
required
Example:

"XAF"

serviceId
integer
Example:

1

service_id
integer
Example:

1

provider
string
Example:

"mtn_cmr"

origin
enum<string>
Available options:
APPLICATION,
PLUGIN
Example:

"APPLICATION"

plugin
string
Example:

"CHECKOUT"

feeBearer
enum<string>
Available options:
CUSTOMER,
MERCHANT
Example:

"CUSTOMER"

customerPaysFees
boolean
deprecated
Example:

true

operation
enum<string>
Available options:
COLLECTION,
DISBURSEMENT
Example:

"COLLECTION"

Response

Devis de fees

code
integer
Example:

200

success
boolean
Example:

true

data
object
locale
string
Example:

"fr"

message
string
Example:

"fees_quote"