Merchant to myPOS Web Checkout |
|
---|---|
API function call |
Description |
This is the standard method for checkout at a shop. The method can be used for card storage also. All sensitive data will be collected on the myPOS Checkout Payment page. Customer interaction needed. |
|
This method enables a myPOS merchant to accept payments on a website or a mobile application. |
|
This is a standard method for checkout when the purchase will be embedded within the external app. All sensitive data will be collected from the external application. |
|
This is a method for storing card data. All sensitive data will be collected from the external application. |
|
This is a method used to update a data of already stored card. All sensitive data will be collected from the external application. |
|
Credit to a customer, e.g. return money. No customer interaction needed. |
|
Make a direct withdrawal transaction (Request money) from a specific myPOS account. No customer interaction needed. |
|
Make a new registration of a mandate reference for Request money transactions from a myPOS account or cancel a previously registered mandate reference. No customer interaction needed. |
|
Returns the status of a previously executed payment. No customer interaction needed. |
|
Send money to another myPOS account. No customer interaction needed. |
|
Create a pre-authorization for an amount to a specific card. All sensitive data will be collected on the myPOS Checkout Payment page. Customer interaction needed. |
|
Create a pre-authorization for an amount to a specific card. |
|
Completes a pre-authorization. |
|
Cancels a pre-authorization. |
|
Get the status of a pre-authorization. |
|
Create an authorization for an amount to an already stored card. |
|
Capture the authorized amount of an already stored card. |
|
Release the authorized amount of an already stored card. |
|
Retrieve a list of Authorizations neither captured nor reversed. |
myPOS Web Checkout to Merchant |
|
---|---|
API function call |
Description |
myPOS Web Checkout will respond with this method on successful payment. The call will be made on the previously supplied URL_Notify. |
|
myPOS Web Checkout will redirect with this method on successful payment. The call will be made on the previously supplied URL_OK. |
|
myPOS Web Checkout will redirect with this method when the customer chooses to cancel the payment. The call will be made on the previously supplied URL_Cancel. |
|
myPOS Web Checkout will notify that a reversal is passed for a previous successful authorization. The merchant should mark the order as not paid (in case, the merchant has received IPCPurchaseNotify method). This is used when myPOS Web Checkout does not receive an HTTP OK from the merchant as a response to the IPCPurchaseNotify method. |
|
IPCPreAuthorization will respond with this method on successful pre-authorization. The call will be made on the previously supplied URL_Notify. |
|
IPCPreAuthorization checkout page will redirect with this method on successful pre-authorization. The call will be made on the previously supplied URL_OK. |
|
IPCPreAuthorization checkout page will redirect with this method when the customer chooses to cancel the pre-authorization. The call will be made on the previously supplied URL_Cancel. |
All commands described here do not include the standard properties discussed in the previous topic. However, the standard properties are mandatory for all commands.