Appexmoney

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

Open Appexmoney in the provider directory and press Connect at Appexmoney Provider Overview page in the New connection section. Choose H2H Merchant account.

Step 2 - Fill in fields and select settings

• Account
• Secret Key 1
• Secret Key 2
• API URL

Choose Currency and Features. You can set these parameters according to available currencies and features for your Appexmoney account (RUB, UZS confirmed), but it is necessary to check details of the connection with your Corefy account manager.

First request to Corefy API (MIN)

What it does: creates a payment-invoice; card data itself is collected and submitted separately by Corefy's checkout/SDK layer, not as part of this request.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8e3dbbb0-17af-4c9a-bedb-93bdac6900a2",
      "service": "payment_card_rub_hpp",
      "currency": "RUB",
      "amount": 100
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6795502c-e27d-4d07-85e0-93245aab9a3f",
      "service": "payment_card_rub_hpp",
      "currency": "RUB",
      "amount": 100,
      "customer": {
        "reference_id": "cus_123",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567"
      }
    }
  }
}

customer.email/customer.phone are optional pass-throughs, falling back to the Constants below if not sent. This flow also supports UZS (payment_card_uzs_hpp). A CVV isn't required for Appexmoney card sales - except for UZS, where a CVV value is still needed and is sourced from the CVV Constant below if your request doesn't supply the card's real one through the checkout/SDK layer.

Extended request (MAX)

Why add extra fields (typical reasons): - Provide additional customer details for compliance/reconciliation - Positively influence conversion rate - Include optional fields required by your specific flow

Options

Options are configured on the Corefy side and affect how Corefy builds provider requests or processes responses.

Currently available options (3)

• send_merchant_url_in_the_description - replaces the payment description with the merchant account's profile website
• use_internal_id_on_reconcile - uses Corefy's own transaction ID instead of Appexmoney's ID when checking payment status
• send_additional_browser_data - sends extended browser/device fingerprint data with the request

Constants (fallback fields)

Constants are static values that Corefy can send to the provider instead of dynamic data from your API request, when those fields are missing in the request.

Priority (predictable rule): 1. If a value is present in the request -> Corefy uses the request value 2. Else if the constant is set -> Corefy uses the constant 3. Else -> provider may reject the request or apply its defaults (depends on provider)

Currently available constants (constant -> Corefy API field)

• EMAIL -> customer.email
• PHONE -> customer.phone
• CVV -> not a request field - a fallback CVV value used only for UZS sales when the real card CVV isn't otherwise available (see the note above).

Connect Merchant account in Corefy Dashboard

Step 1 - Open connection form

Open Appexmoney in the provider directory and press Connect at Appexmoney Provider Overview page in the New connection section. Choose Merchant account.

Step 2 - Fill in fields and select settings

• Account
• First Secret Key
• Second Secret Key
• API URL

Choose Currency and Features - which local methods are available depends on what's enabled on your Appexmoney account (see Additional info) - check with your Corefy account manager.

First request to Corefy API (MIN)

What it does: creates a payment-invoice and returns a redirect link to Appexmoney's hosted payment page.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "0dde9e79-2c64-4703-adaf-93d710633401",
      "service": "papara_try_hpp",
      "currency": "TRY",
      "amount": 100
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "7976b4ce-fadd-4585-baa0-6b02c65351dc",
      "service": "papara_try_hpp",
      "currency": "TRY",
      "amount": 100,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567"
      }
    }
  }
}

This connector also supports payfix_try_hpp (TRY, Payfix), card_transfer_azn_hpp (AZN), and payment_card_rub_hpp (RUB) as alternate services for this same flow - which ones are enabled depends on your account.

Extended request (MAX)

Why add extra fields (typical reasons): - Provide additional customer details for compliance/reconciliation - Positively influence conversion rate - Include optional fields required by your specific flow

Options

Options are configured on the Corefy side and affect how Corefy builds provider requests or processes responses.

Currently available options (2)

• on_notify_email - tells Appexmoney whether to send its own email notification to the customer
• on_notify_phone - tells Appexmoney whether to send its own SMS notification to the customer

Constants (fallback fields)

Constants are static values that Corefy can send to the provider instead of dynamic data from your API request, when those fields are missing in the request.

Priority (predictable rule): 1. If a value is present in the request -> Corefy uses the request value 2. Else if the constant is set -> Corefy uses the constant 3. Else -> provider may reject the request or apply its defaults (depends on provider)

Currently available constants (constant -> Corefy API field)

• FIRST_NAME -> customer.name (first part)
• LAST_NAME -> customer.name (second part)
• EMAIL -> customer.email
• PHONE -> customer.phone

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

Open Appexmoney in the provider directory and press Connect at Appexmoney Provider Overview page in the New connection section. Choose Provider account.

Step 2 - Fill in fields and select settings

• Account
• First Secret Key
• Second Secret Key
• API URL
• Test Mode -> (enable if you are using sandbox credentials)

First request to Corefy API (MIN)

What it does: creates a payout-invoice and sends funds to a card.

Payout - MIN

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "0dde9e79-2c64-4703-adaf-93d710633401",
      "service": "payment_card_rub",
      "currency": "RUB",
      "amount": 100,
      "customer": {
        "reference_id": "cus_123"
      },
      "fields": {
        "card_number": "4111111111111111"
      }
    }
  }
}

Payout - MAX

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "7976b4ce-fadd-4585-baa0-6b02c65351dc",
      "service": "payment_card_rub",
      "currency": "RUB",
      "amount": 100,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith"
      },
      "fields": {
        "card_number": "4111111111111111"
      }
    }
  }
}

fields.card_number is required. This connector also supports payouts in USD, EUR, KZT, AZN, and UZS (use payment_card_usd/payment_card_eur/payment_card_kzt/payment_card_azn/payment_card_uzs as the service code).

Extended request (MAX)

Why add extra fields (typical reasons): - Provide additional customer details for compliance/reconciliation - Positively influence conversion rate - Include optional fields required by your specific flow