Skip to content

Introduction

Basil Miller edited this page Dec 10, 2020 · 4 revisions

This page describes the integration process steps and general API information.

1. Integration process

Merchant registration

Before you get an account to access Payment Platform, you must provide the following data to the Payment Platform administrator.

Data Description
IP List List of your IP addresses, from which requests to Payment Platform will be sent Notification
URL URL which will be receiving the notifications of the processing results of your request to Payment Platform
Contact Email Email address of Responsible Person who will monitor transactions, conduct refunds, etc.

Note: Notification URL is mandatory if your account supports 3D-Secure. The length of Notification URL should not be more than 255 symbols.

With all Payment Platform POST requests at Notification URL the Merchant must return the string "OK" if he successfully received data or return "ERROR".

You should get the following information from the administrator to begin working with the Payment Platform.

Info Description
CLIENT_KEY Unique key to identifying the account in Payment Platform (used as request parameter)
CLIENT_PASS Password for Client authentication in Payment Platform (used for calculating hash parameter)
PAYMENT_URL URL to request the Payment Platform

What to do with this information? Follow the setup guide.

2. Brief description of the interaction with Payment Platform

SDK supports the following actions:

Action Description
SALE Creates SALE or AUTH transaction
CAPTURE Creates CAPTURE transaction
CREDITVOID Creates REVERSAL or REFUND transaction
GET_TRANS_STATUS Gets status of the transaction in Payment Platform
GET_TRANS_DETAILS Gets details of the order from Payment platform
RECURRING_SALE Creates SALE or AUTH transaction using previously used cardholder data

SDK supports the following transaction results and statuses:

Akurateco

The Akurateco Android SDK - https://akurateco.com

Clone this wiki locally