FrameAppWS

AMDCReversarPagoRQ

The following routes are available for this service:
All Verbs	/pago/ReversarPago

**AMDCReversarPagoRQ** Parameters:
Name	Parameter	Data Type	Required
IdTransaccionBanco	query	string	No
Banco	query	string	No
Sucursal	query	string	No
Usuario	query	string	No
Terminal	query	string	No

**DatosBanco** Parameters:
Name	Parameter	Data Type	Required
Banco	form	string	No
Sucursal	form	string	No
Usuario	form	string	No
Terminal	form	string	No

**AMDCReversarPagoRS** Parameters:
Name	Parameter	Data Type	Required
PagoReversadoRespuesta	form	ResultadoTransaccion	No
TranId	form	string	No
Code	form	string	No
InfoMsg	form	string	No

**CoreRes** Parameters:
Name	Parameter	Data Type	Required
TranId	form	string	No
Code	form	string	No
InfoMsg	form	string	No

**ResultadoTransaccion** Parameters:
Name	Parameter	Data Type	Required
Resultado	form	string	No
MensajeResultado	form	string	No
FechaTransaccion	form	string	No

To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json

To embed the response in a jsonp callback, append ?callback=myCallback

HTTP + JSON

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /pago/ReversarPago HTTP/1.1 
Host: soluser-recaudo.sgsas.co 
Accept: application/json
Content-Type: application/json
Content-Length: length

{"IdTransaccionBanco":"String","Banco":"String","Sucursal":"String","Usuario":"String","Terminal":"String"}

HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length

{"PagoReversadoRespuesta":{"Resultado":"String","Mensaje":"String","FechaTransaccion":"String"},"TranId":"String","Code":"String","InfoMsg":"String"}