/Completion

POST

/Completion

The /Completion request is used to finished a preauthorized payment in the case of a two-phase payment.
A merchant can perform this request if it has the relevant permissions in the system.

Request

Header Params

ExtSystemid

string

required

The identifier of the external system (ES) that generated the request. The identifier agrees with UKRKART during the registration of the ES

>= 1 characters<= 50 characters

Example:

ECOM_GOLD_BANK

string

required

External system login received from UKRKARD during registration

>= 1 characters<= 30 characters

Example:

SECURE_LOGIN

password

string

required

External system password received from UKRKARD during registration

>= 1 characters<= 30 characters

Example:

SECURE_PASSWORD

orderNumber

string

required

Number (identifier) of the order in the merchant’s online
store system. It is unique for every store in the system and
is generated on the order registration

>= 1 characters<= 32 characters

Example:

1234

orderId

string

optional

Number generated by wsGate after the registration of the order.

>= 36 characters<= 36 characters

Example:

dbafea6c-3394-4f6a-a0d2-21d3d8e93e42

RegDate

string <date-time>

required

Date/time of the request in yyyy-MM-dd HH:mm:ss format

<= 19 characters

Example:

2023-09-12 12:16:00

Match pattern:

YYYY-MM-DD hh:mm:ss

x-uws-clientdn

string

required

The specified value must be equal to the value specified in the Common Name (CN) field for the client's SSL certificate

<= 500 characters

Example:

GOLDENBANK

Content-Type

string

optional

application/json;charset=UTF-8

Example:

application/json;charset=UTF-8

charset

string

optional

UTF-8

Example:

UTF-8

enum<string>

required

application/json

Allowed value:

application/json

Body Params application/json

orderData

object

required

Transaction registration data

amount

number

150000

required

Order amount in the minor denomination (for example, cents). You can use a verification operation such as Debit Verify (which is similar to a Visa account and a Mastercard account) for a zero amount for additional 3DS authentication. For these operations, you must use the primary method /Payment with a zero amount. 3DS authentication will be present for MPS Visa and Mastercard cards. For NPS Prostir cards, the primary operation will be to verify the cloud record.

<= 10000000000000000000

currency

string

optional

Payment currency code in the ISO 4217 format. If it is not indicated, it must be entered equal to the currency code according to the rules (980 - UAH)

>= 3 characters<= 3 characters

externalFee

string

optional

Fee amount in the minor denomination of the currency. This can only be done for the p2pTransfer method

<= 9 characters

description

string

required

Free form description of the order.

<= 512 characters

pageData

object

required

External system page data

language

string

required

The language of the current page session

>= 2 characters<= 2 characters

Example:

returnUrl

string

required

URL to which the customer is redirected after a successful payment. The address must be specified in full, including the protocol used (for example, "https://test.ua" instead of test.ua). Otherwise, the user will be redirected to the default address

<= 512 characters

failUrl

string

required

Web address to which the customer is redirected if the payment fails. The address must be specified in full, including the protocol used (for example, https://test.ua instead of test.ua). Otherwise, the user will be redirected by default

<= 512 characters

jsonParams

object

optional

Block for transmitting additional merchant parameters.

merchantIdType

string

optional

Document type
Possible values:
IDTP01 – Passport
IDTP0010 – Taxpayer ID (ІПН)
IDTP0016 – Company registration number (код ЄДРПОУ)
Example:
{"name":"merchantIdType","value":"IDTP01"}

merchantIdNumber

string

optional

Document details
varchar (13)
Example:
{"name":"merchantIdNumber","value":"ABCDXYZ124"}

fmparam

object

optional

Block for transmitting a list of additional parameters used to implement the regulator's requirements for transmitting information about the payer in a payment transaction, and used for financial monitoring. The obligation to transmit parameters in the specified tag for each method is specified in the requirements (application) of the acquiring bank for registration of terminals.

ReceiverCNAME

string

optional

Recipient name (legal entity)
(Only characters in encoding (UTF-8) are used, without using Unicode escapes!)

ReceiverEDRPOU

string

optional

Recipient's EDRPOU (legal entity) 8 digits

>= 8 characters<= 8 characters

Match pattern:

^[0-9]

ReceiverIBAN

string

optional

IBAN number (legal entity) of the recipient in the format for Ukraine.
Must start with UA, followed by 2 check digits, 6 characters of the MFO of the corresponding bank, and 19 characters of the bank account number. Total length — 29 characters.
Only IBANs issued by Ukrainian banks are supported.

>= 29 characters<= 29 characters

Match pattern:

^UA\d{2}\d{6}\d{19}$

SenderCNAME

string

optional

Name of the payer (legal entity)
(Only characters in encoding (UTF-8) are used, without using Unicode escapes!)

SenderEDRPOU

string

optional

Payer's Unified State Register of Accounts (legal entity) 8 digits

>= 8 characters<= 8 characters

SenderIBAN

string

optional

IBAN number of the payer (legal entity) in the format for Ukraine.

Must start with UA, followed by 2 check digits, 6 characters of the MFO of the corresponding bank, and 19 characters of the bank account number. Total length — 29 characters.
Only IBANs issued by Ukrainian banks are supported.

>= 29 characters<= 29 characters

Match pattern:

^UA\d{2}\d{6}\d{19}$

SenderPIB

string

optional

Full name of the payer (individual)
(Only characters in encoding (UTF-8) are used, without using Unicode escapes!)

SenderITN

string

optional

Taxpayer's INN (individual) 10 digits
(or passport number and series, if the person does not have a INN)

ReceiverPIB

string

optional

Full name of the recipient (individual)
(Only characters in encoding (UTF-8) are used, without using Unicode escapes!)

ReceiverITN

string

optional

TIN of the recipient (individual) 10 digits
(or passport number and series, if the person does not have a TIN)

TranID

string

optional

Transaction identifier in external systems, can be used as additional information for reconciliations if required by the acquiring bank

Example

{
    "orderData": {
        "amount": 10000,
        "currency": 980,
        "description": "Операція #304324"
    },
    "pageData": {
        "language": "uk"
    }
}

Request samples

Shell

JavaScript

Java

Swift

PHP

Python

HTTP

Objective-C

Ruby

OCaml

Dart

curl --location --request POST 'https://mock.apidog.com/m1/537337-0-default/Completion' \
--header 'ExtSystemid: ECOM_GOLD_BANK' \
--header 'login: SECURE_LOGIN' \
--header 'password: SECURE_PASSWORD' \
--header 'orderNumber: 1234' \
--header 'orderId: dbafea6c-3394-4f6a-a0d2-21d3d8e93e42' \
--header 'RegDate: 2023-09-12 12:16:00	' \
--header 'x-uws-clientdn: GOLDENBANK' \
--header 'charset;' \
--header 'accept;' \
--header 'Content-Type: application/json' \
--data-raw '{
    "orderData": {
        "amount": 10000,
        "currency": 980,
        "description": "Операція #304324"
    },
    "pageData": {
        "language": "uk"
    }
}'

Responses

🟢200OK

application/json

Body

orderParam

object

required

orderStatus

integer

required

orderId

string

required

orderAuthParam

object

required

Example

{
    "orderParam": {
        "orderStatus": 2,
        "orderId": "f390136a-77ad-43e1-9593-3ec72c791834",
        "orderAuthParam": {
            "approvalCode": "107429",
            "authCode": 2
        }
    }
}

Modified at 2025-06-26 12:35:32

/CancelPreauthorization

/Confirm