API · processModification

API v1

An MCP tool wraps this operation: Sales and transactions.

POST /api/v1/processModification

What it does#

Modifies an already processed transaction: capture, refund or reversal.

Requires the API bearer token in the Authorization header — see authentication.

orderNumberstringrequired#

Number of the order sent in the original charge.

typestringrequired#

Type of modification.

amountstringrequired#

Amount to modify.

keystringrequired#

Key associated with the customer. Obtained in Admin panel · Platform integrations.

The <...> values are placeholders: replace them with your own credentials and data.

{
  "orderNumber": "1214352",
  "type": "2",
  "amount": "1.00",
  "key": "<api_key>"
}

type: "100" means the modification was processed; its outcome is in ReasonCode and ReasonCodeDescription. 1101 = approved.

Approved:

{"type":"100","transactionId":954183,"ReasonCode":"1101","ReasonCodeDescription":"Transaccion aprobada","OrderHash":"<order_hash>"}

Rejected:

{"type":"100","transactionId":954183,"ReasonCode":"3","ReasonCodeDescription":"Invalid Retrieval reference number","OrderHash":"<order_hash>"}

Error (type 300 or 400):

{"type":"400","message":"Order number: TYP974_172 does not exist"}

typestring#

"100" indicates that the modification was processed.

transactionIdnumber#

Transaction identifier.

ReasonCodestring#

Result code of the modification.

ReasonCodeDescriptionstring#

Result text.

OrderHashstring#

Order hash. See the note about orderHash in webhooks.

To interpret a response that is not a success, see how to read an error response.

Last verified: 2026-10-22