Aimed at Project Managers, this matrix enables you to assess the logistics involved in integrating with the Mastercard Payment GatewayAPI.
Both the protocols, REST and NVP, offer the same functionality; however, there might be certain factors to consider before you make your decision.
| REST | NVP | |
|---|---|---|
When to Use |
With complex integrations that include a web application connected to an application server, database, and web server. This protocol is also suitable for simple integrations. | With simple integrations that include a web page submitting a form to the web server. |
Technical Skills Required |
It's recommended that you have basic knowledge of HTTP and the skills to formulate an HTTP request in the preferred server-side scripting language. Basic knowledge of the JSON data-interchange format is also recommended. See http://www.json.org/ |
Basic knowledge of HTTP and the skills to formulate an HTTP request in the preferred server-side scripting language. |
Software Requirements |
None | None |
Authentication |
Authentication information such as password are included in the HTTP headers rather than the body of the request. | Authentication information is included in the body of the Transaction Request. |
| Usage of HTTPS POST | POST is typically used when you want the system to create a new entry in the collection addressed by the URL. | POST is the only valid HTTP method for the NVP protocol and thus used with all transaction operations. |
| Usage of HTTPS PUT | PUT is typically used when the URL contains a member of the collection. | PUT is not a supported method with the NVP protocol. |
| Usage of HTTPS GET | GET is only enabled for retrieve operations. | GET is not a supported method with the NVP protocol. |