Create or modify funding amounts
Used to create or modify MerchantFundingAmount for approved, non-PIN-debit, cardholder-debit or credit Transactions.
Request Constraints:
- Can contain 1 to 10,000 Transaction(s)
- Must not contain any debit Transactions that have been settled
- Can contain credit transactions that have been settled
- Must not contain duplicate Transactions
- Debit transactions can be specified by either retrievalReferenceNumber or id (transactionId), but not both
- Credit transactions can only be specified by id (transactionId)
HTTP Status Code Evaluation: Status Code conditions are assessed in the following order, and the first matching condition determines the response:
- 400 - Request body issues
- 401 - Authentication failure
- 403 - Profile inactive
- 500 - Server error
- 200 - Success (none of above conditions met)
Request Body
Content type: application/json
Required1 field
transactionsarray<object>Example Request
Sample payload with starter values. Replace with your own data.
{
"transactions": [
{
"id": "ABC12345678901234567890123456789",
"merchantFundingAmounts": [
{
"merchantId": "9999999999",
"amount": "10000"
},
{
"merchantId": "8888888888",
"amount": "500"
}
]
},
{
"id": "XYZ12345678901234567890123456789",
"merchantFundingAmounts": [
{
"merchantId": "9999999999",
"amount": "10000"
},
{
"merchantId": "8888888888",
"amount": "500"
}
]
}
]
}Responses
Request processed successfully.
Note: A 200 response may still contain transaction-level errors in the transactionLevelErrors array. Check successfulTransactionCount vs transactionCount to determine if all transactions succeeded.
Common2 fields
transactionCountstringsuccessfulTransactionCountstringWhen Provided3 fields
errorCodestringenumerrorMessagestringtransactionLevelErrorsarray<object>Other Fields2 fields
merchantFundingAmountCountstringamountsSumstringExample response
{
"transactionCount": "2",
"merchantFundingAmountCount": "4",
"amountsSum": "21000",
"successfulTransactionCount": "1",
"errorCode": "",
"errorMessage": "",
"transactionLevelErrors": [
{
"transactionId": "XYZ12345678901234567890123456789",
"retrievalReferenceNumber": "",
"errorCode": "100",
"errorMessage": "unknown transactionId"
}
]
}Bad Request - Request body cannot be processed.
Conditions:
- Unsupported content type
- Malformed body
- Values exceeding the max field size
- Values of incorrect data type
- Too many or not enough records
Note: No response body is provided for this error.
Unauthorized - Authentication failure.
Conditions:
- The provided profileId is unknown
- The provided profileKey is incorrect for the provided profileId
Note: No response body is provided for this error.
Forbidden - Profile inactive.
Conditions:
- The provided profileId and profileKey is known and correct
- But the profileId is associated with a profile that is no longer active (suspended or closed)
Note: No response body is provided for this error.
Internal Server Error - The server encountered an unexpected error and could not process the request.
Note: No response body is provided for this error.
Code samples
Copy-paste ready code in your preferred language.
API call
curl -X POST "https://{host}{basePath}/funding-amounts" \
-H "Content-Type: application/json" \
-H "Authorization: Basic <base64(profileId:profileKey)>" \
-d '{
"transactions": [
{
"id": "ABC12345678901234567890123456789",
"merchantFundingAmounts": [
{
"merchantId": "9999999999",
"amount": "10000"
},
{
"merchantId": "8888888888",
"amount": "500"
}
]
},
{
"id": "XYZ12345678901234567890123456789",
"merchantFundingAmounts": [
{
"merchantId": "9999999999",
"amount": "10000"
},
{
"merchantId": "8888888888",
"amount": "500"
}
]
}
]
}'