Get Money Transfer Charge #
This endpoint calculates the charge for a money transfer.
Request #
-
URL:
https://crm-api-test.10npay.com/api/v1/IndividualPayment/get-money-transfer-charge
-
Method:
POST
-
Headers:
-
accept: text/plain
-
Authorization: Bearer {Token}
-
Content-Type: application/json-patch+json
-
Path Parameters
-
id
: The user ID (e.g.,132
).
Request Body
{
"customerAccount": "string",
"amount": 0,
"id": 0,
"paymentType": "string"
}
Example
{
"customerAccount": "BG56TEPJ40131000100196",
"amount": 1.22,
"id": 0,
"paymentType": "P2IBAN"
}
Curl Command Example
curl -X 'POST' \
'https://app-api-test.10npay.com/api/v1/IndividualPayment/132/get-money-transfer-charge' \
-H 'accept: text/plain' \
-H 'Authorization: Bearer {Token}' \
-H 'Content-Type: application/json-patch+json' \
-d '{
"customerAccount": "BG56TEPJ40131000100196",
"amount": 1.22,
"id": 0,
"paymentType": "P2IBAN"
}'
Server Response Codes #
-
201 Created #
-
Description: The money transfer charge was successfully calculated.
-
Response Body:
-
{
"accountNo": "string",
"accountBalance": 0,
"accountCurrency": "string",
"transactionAmount": 0,
"transactionCurrency": "string",
"transactionFee": 0,
"transactionFeeCurrency": "string"
}
Example:
{
"accountNo": "00100196",
"accountBalance": 1.0,
"accountCurrency": "BGN",
"transactionAmount": 1.22,
"transactionCurrency": "BGN",
"transactionFee": 1.0,
"transactionFeeCurrency": "BGN"
}
-
400 Bad Request #
-
Description: The request could not be understood or was missing required parameters.
-
Response Body:
-
{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"additionalProp1": "string",
"additionalProp2": "string",
"additionalProp3": "string"
}
Example:
{
"errors": {
"Error": [
"Invalid Account"
]
},
"type": "https://tools.ietf.org/html/rfc7231#section-6.5.1",
"title": "Bad Request",
"status": 400,
"traceId": "00-97cc33f14571fcfd45512cc85610b614-1de79ea3bad5df5e-01"
}
Snippet #
Peer-to-peer money transfer #
URL
https://crm-api-test.10npay.com/api/v1/IndividualPayment/source-individualId/{sourceIndividualId}/beneficiary-individualId/{beneficiaryIndividualId}/p2p-money-transfer
Method: POST
Example
https://crm-api-test.10npay.com/api/v1/IndividualPayment/source-individualId/590/beneficiary-individualId/740/p2p-money-transfer
Request #
Headers
-
accept: text/plain
-
Authorization: Bearer {token}
-
Content-Type: application/json-patch+json
Path Parameters
-
sourceIndividualId
: The ID of the source individual. -
beneficiaryIndividualId
: The ID of the beneficiary individual.
Request Body
The request body should be a JSON object with the following properties:
Field |
Type |
Description |
---|---|---|
|
string |
The source customer’s account number. |
|
string |
The beneficiary customer’s account number. |
|
number |
The amount of money to transfer. |
|
string |
Notes regarding the payment. |
{
"sourceCustomerAccount": "BG56TEPJ40131000100196",
"beneficiaryCustomerAccount": "BG59TEPJ40131000100142",
"transactionAmount": 1.22,
"paymentNotes": "test"
}
Curl Example
curl -X 'POST' \ 'https://app-api-test.10npay.com/api/v1/IndividualPayment/source-individualId/132/beneficiary-individualId/570/p2p-money-transfer' \ -H 'accept: text/plain' \ -H 'Authorization: Bearer {token}' \ -H 'Content-Type: application/json-patch+json' \ -d '{ "sourceCustomerAccount": "BG56TEPJ40131000100196", "beneficiaryCustomerAccount": "BG59TEPJ40131000100142", "transactionAmount": 1.22, "paymentNotes": "test" }'
Responses #
200 Success #
A successful response returns a string which is the reference number of the transaction.
Example Response
TNP0004241580001
400 Bad Request #
A bad request response returns a JSON object detailing the error.
Response Body
Field |
Type |
Description |
---|---|---|
|
string |
The type of error. |
|
string |
The title of the error. |
|
number |
The HTTP status code. |
|
string |
A detailed description of the error. |
|
string |
The instance of the error. |
|
string |
Additional properties for more information. |
|
string |
Additional properties for more information. |
|
string |
Additional properties for more information. |
{
"errors": {
"Error": [
"SameIbanAccounts"
]
},
"type": "https://tools.ietf.org/html/rfc7231#section-6.5.1",
"title": "Bad Request",
"status": 400,
"traceId": "00-e5095882753957d4e0a0af7821756084-7e7fc0e8f74e65bc-01"
}
404 Not Found #
A not found response returns a JSON object indicating that the specified resource could not be found.
Response Body
Field |
Type |
Description |
---|---|---|
|
string |
The type of error. |
|
string |
The title of the error. |
|
number |
The HTTP status code. |
|
string |
A detailed description of the error. |
|
string |
The instance of the error. |
|
string |
Additional properties for more information. |
|
string |
Additional properties for more information. |
|
string |
Additional properties for more information. |
500 Server Error #
Notes
-
Ensure the
Authorization
header contains a valid Bearer token. -
The
transactionAmount
should be a positive number. -
Proper error handling should be implemented based on the status codes and response bodies provided above.