Payture InPay
InPay is an easy way to accept payments without saving cards. With the InPay programming interface, card data is entered on the Payture payment gateway side, so the Merchant does not need PCI DSS verification – Payture ensures data protection.
The Customer stays on the Merchant's website only until they enter their card details. To pay, the Customer is redirected to the secure Payture payment page. After the payment, the Customer is informed of the result and returned to the Merchant's page, and the Merchant receives notifications with the payment results.
Payment page
The Merchant can either redirect the Customer directly to the Payture payment page or open it in an iframe on the store's website or in a WebView in a mobile app.
The Merchant can customize the look of the standard payment page. To do this, the Merchant needs to prepare one or more payment page templates. You can find information and detailed technical specifications for creating templates here.
Features
In addition to standard bank card payments, the Payture payment page supports the Apple Pay, Google Pay, Samsung Pay and SberPay mobile payment methods. Using them does not require complex changes on the Merchant's side — all the necessary integrations are already implemented on the Payture side.
For additional Customer verification, the Payture payment page performs 3-D Secure authentication if this procedure is available for the card being used.
Standard set of e-commerce operations for the InPay interface
| Init | Initializes a one-step or two-step payment — creates the payment session required to open the payment page |
| Pay | Opens the payment page on the Payture payment gateway side |
| Charge | Captures funds held on the Customer's card as part of a two-step payment |
| Unblock | Releases the hold on funds on the Customer's card |
| Refund | Refunds funds to the Customer's card in full or in part |
| GetState | Retrieves the current status of a payment |
