...¶

Website: ...

                              **CG**

Set up Account H2H merchant account¶

Step 1: Create Merchant Account¶

To create an account send connection request at the ... or contact manager directly. Submit the required documents to verify your account and gain access.

Step 2: Get required credentials¶

Credentials that have to be issued:

• ...
• ...
• ...__currency → choose currency (You can set these parameters according to available currencies and features for your ... wallets and services, but it's necessary to check details of the connection with your Corefy account manager.)

Connect Merchant Account¶

Step 1. Connect H2H account at the Corefy Dashboard¶

Press Connect at ... Provider Overview page in 'New connection' section and choose H2H Merchant account option to open Connection form.

Enter credentials:

• ...
• ...
• ...

                          **PG/POG**

Set up Account Provider account¶

Step 1: Create Provider account¶

To create an account send connection request at the ... or contact manager directly. Submit the required documents to verify your account and gain access.

Step 2: Get required credentials¶

Credentials that have to be issued:

• ...
• ...
• ...

Connect Provider Account¶

Step 1. Connect Provider account at the Corefy Dashboard¶

Press Connect at ... Provider Overview page in 'New connection' section and choose Provider account option to open Connection form.

Enter credentials:

• ...
• ...
• ...

API examples:¶

Minimum data set to create a payment invoices for ... service¶

SALE
.
.

Maximum data set to create a payment invoices for ... service¶

SALE
.
.

Minimum data set to create a payment invoices for ... service¶

PAYMENT
.
.

Maximum data set to create a payment invoices for ... service¶

PAYMENT
.
.

Minimum data set to create a payout invoices for ... service¶

PAYOUT
.
.

Maximum data set to create a payout invoices for ... service¶

PAYOUT
.
.

Constants¶

If some parameters are not sent in the transaction creation request, they will take the values from the set constants.

Here is a list of constants with their corresponding parameters:

• FIRST_NAME → customer [address] [first_name]
• LAST_NAME → customer [address] [last_name]
• COUNTRY → customer [address] [country]
• STATE → customer [address] [state]
• CITY → customer [address] [city]
• ADDRESS → customer [address] [address]
• POST_CODE → customer[address][post_code]
• EMAIL → customer [address] [email]
• PHONE → customer [address] [phone]
• DATE_OF_BIRTH → customer [date_of_birth]
• FULL_ADDRESS → customer [address] [full_address]
• REGION → customer [address] [region]
• PAYER_MIDDLE_NAME → customer [address] [middle_name]
• PAYER_ZIP → customer [address] [zip]
• TERM_URL_TARGET → customer [address] [url_target]
• СUSTOMER_REFERENCE_ID → customer [reference_id]

Provider Options¶

• ignore_callback
  • for cascading to work correctly, we exclude the possibility of finalizing payments using asynchronous callbacks, ignore the callback, do not change the status of the transaction on it in any way and rely only on the status request for finalization (Reconciliation)

Default values¶

If some parameters are not passed in the request to create a transaction and the corresponding constants have no values, then default values will be passed instead.

Here is the list of default values with their corresponding parameters:

• TEST_TEST → '192.168.0.1';
• TEST_TEST → '_test';