|
Further information can be found on the webpage of MasaPay (https://www.masapay.com/).
|
If the synchronous response from MasaPay returns the payment result as 00 (Accepted) or 12 (Pending), MasaPay will send the final status in the asynchronous notification subsequent to the synchronous response. It’s also possible for the synchronous result 11 (Failed). Only 10 (Successful) is the final status either in the synchronous or in the asynchronous response.
MasaPay process flow over payssl.aspx
MasaPay process flow over direct.aspx
To process a payment with MasaPay, please use the following URL:
payssl.aspx |
|
Parameters for credit card payments with MasaPay
|
Return parameters for URLSuccess, URLFailure and URLNotify with MasaPay
To carry out a TLS credit card payment with MasaPay via a Server-to-Server connection, please use the following URL:
direct.aspx |
|
Request parameters of credit card payment with MasaPay per server to server
The following table describes the result parameters that the sends back as response in a server-to-server connection, or transmits to your URLNotify when asynchronous notification from MasaPay has arrived. If you have specified the Response=encrypt parameter, the following parameters are sent Blowfish encrypted to your system:
pls. be prepared to receive additional parameters at any time and do not check the order of parameters
the key (e.g. MerchantId, RefNr) should not be checked case-sentive
|
Response parameters of credit card payment with MasaPay per server to server connection
Captures are possible via a Server-to-Server connection. To perform a capture via a Server-to-Server connection please use the following URL:
capture.aspx |
|
Request parameters for capture of credit card payment with MasaPay
The following table describes the result parameters that the sends back as response in a server-to-server connection, or transmits to your URLNotify when asynchronous notification from MasaPay has arrived. If you have specified the Response=encrypt parameter, the following parameters are sent Blowfish encrypted to your system:
pls. be prepared to receive additional parameters at any time and do not check the order of parameters
the key (e.g. MerchantId, RefNr) should not be checked case-sentive
|
Response parameters for capture of credit card payment with MasaPay
Credits (refunds) are possible via a Server-to-Server connection. If you refer to a capture for a Credit, the amount of the Credit is limited to the amount of the previous capture.
To carry out a credit with a reference transaction, please use the following URL:
credit.aspx |
Request parameters for credit of credit card payment with MasaPay
The following table describes the result parameters that the sends back as response in a server-to-server connection, or transmits to your URLNotify when asynchronous notification from MasaPay has arrived. If you have specified the Response=encrypt parameter, the following parameters are sent Blowfish encrypted to your system:
pls. be prepared to receive additional parameters at any time and do not check the order of parameters
the key (e.g. MerchantId, RefNr) should not be checked case-sentive
|
Response parameters for credit of credit card payment with MasaPay
A credit card authorisation lowers the customer's credit line. can reverse an authorisation so that it no longer block the limit any more. Reversals are possible via a Server-to-Server connection with the following URL:
reverse.aspx |
Notice: Reverse.aspx does not only reverse authorisations, but any LAST TRANSACTION STAGE!! If the last transaction was a capture, Reverse.aspx initiates the reverse, e.g. a credit. Therefore, the utmost caution is urged. Use is at your own risk. We recommend checking the transaction status with Inquire.aspx before using Reverse.aspx.
|
Request parameters for reversal of credit card payment with MasaPay
The following table describes the result parameters that the sends back as response in a server-to-server connection, or transmits to your URLNotify when asynchronous notification from MasaPay has arrived. If you have specified the Response=encrypt parameter, the following parameters are sent Blowfish encrypted to your system:
pls. be prepared to receive additional parameters at any time and do not check the order of parameters
the key (e.g. MerchantId, RefNr) should not be checked case-sentive
|
Response parameters for reversal of credit card payment with MasaPay