Create Adjustment
Changed onUse the Create Adjustment endpoint to move funds into or out of a customer account. Transactions using this endpoint are returned by the <a href="ref:post_getaccountoverview" target="_blank">Get Account Overview</a> endpoint only after several seconds have elapsed. To drive an account negative using this endpoint, set the ALWNB parameter at the provider level.
Consult the <a href="doc:creating-an-adjustment" target="_blank">Creating an Adjustment</a> guide for instructions on using this endpoint.
Duplicate requests
When this endpoint returns status_code: 24 (Duplicate transaction) because the same transactionId was already used successfully for Create Adjustment, response_data contains the same fields as a successful response (status_code: 0): adjustment_trans_id, transaction_id, old_balance, and new_balance. Use those values to update your records without a separate lookup. This is especially useful when a prior call timed out after the adjustment was committed: retrying with the same transactionId recovers the original result.
[block:callout]
{ "type": "warning", "title": "Warning", "body": "This endpoint requires a positive integer less than 9223372036854775807 (sys.maxint in Python 2 or sys.maxsize in Python 3) for transactionId rather than the alphanumeric string that all other endpoints use. The Reverse Adjustment endpoint uses this integer to identify the transaction to reverse out." } [/block]
Request
- Base URLapi-{corename}.{env}.gpsrv.com/intserv/4.0/ (relative, and the document’s source URL is not known)
- URLapi-{corename}.{env}.gpsrv.com/intserv/4.0/createAdjustment
- Authnone declared
Request body application/x-www-form-urlencoded
Example request
{
"apiLogin": "AbC123-9999",
"apiTransKey": "4sb62fh6w4h7w34g",
"transactionId": 164736451002,
"accountNo": "074103447228",
"amount": 25.5,
"description": "One time payroll load.",
"debitCreditIndicator": "D",
"location": "a455-3483",
"disputeId": "21010000000D"
}Response
Changes
- info
endpoint added
- info