Any.Money

Comfortable payment service provider with integrated analytical system.

Supports in this guide: Payments, Payouts

Provider website: any.money

What you need to do for start processing transactions (brief summary)

Choose account type
Get your credentials (from Any.Money)
Connect in Dashboard
Send an API request

Choose account type

Any.Money can be connected in different ways (depending on your needs):

If you do card payments -> choose H2H Merchant account
If you do QIWI payments, or any of the supported payouts -> choose Provider account

Any.Money does not currently support card payments through a Provider account, or payouts through the H2H Merchant account. If you're not sure which one to use, confirm with your Corefy account manager.

Prerequisites: get from Any.Money

Authorise on the Any.Money website, create a merchant, and submit the required documents to verify your account. H2H Merchant account and Provider account are separate connections, but both use the same style of credentials issued per connection:

Merchant ID -> Corefy field merchant.
Signature key -> Corefy field signature_key.
Fee strategy -> Corefy field fee_strategy -> Internal (you pay the fee, not shown to the customer) or External (the customer pays the fee on the checkout page).

Note

If you need to whitelist IPs on Any.Money's side, ask your account manager and provide Corefy's IP list from the integration docs.

Payments processing (connect H2H Merchant account, create payment-invoice)

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

Merchant ID
Signature key
Fee strategy -> Internal or External
Test Mode -> (enable if you are using sandbox credentials)

Success

You have connected Any.Money H2H Merchant account!

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": "1a2b3c4d-5e6f-4a7b-8c91-2d3e4f5a6b7c",
      "service": "payment_card_uah_hpp",
      "currency": "UAH",
      "amount": 100
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "2b3c4d5e-6f7a-4b8c-8d02-3e4f5a6b7c8d",
      "service": "payment_card_uah_hpp",
      "currency": "UAH",
      "amount": 100,
      "customer": {
        "reference_id": "cus_123",
        "email": "customer@example.com"
      }
    }
  }
}

Important

customer.email is optional and, when sent, is forwarded to Any.Money as the client's email.
No Constants are configured for this connector - if a customer field is missing, it's simply not sent.
Supported currencies for card payments are UAH and KZT.

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

Refunds

Any.Money does not support refunds on the H2H Merchant account.

Payments processing (connect Provider account, create payment-invoice)

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

Merchant ID
Signature key
Fee strategy -> Internal or External
Test Mode -> (enable if you are using sandbox credentials)

Success

You have connected Any.Money Provider account!

First request to Corefy API (MIN)

What it does: creates a payment-invoice and redirects the customer to Any.Money's hosted payment page to complete a QIWI wallet payment.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "3c4d5e6f-7a8b-4c9d-8e02-3f4a5b6c7d8e",
      "service": "qiwi_rub",
      "currency": "RUB",
      "amount": 100
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "4d5e6f7a-8b9c-4d0e-8f13-4a5b6c7d8e9f",
      "service": "qiwi_rub",
      "currency": "RUB",
      "amount": 100,
      "customer": {
        "reference_id": "cus_123",
        "email": "customer@example.com"
      },
      "fields": {
        "phone": "79001234567"
      }
    }
  }
}

Important

fields.phone is optional - when sent, it is forwarded to Any.Money as the QIWI wallet phone number (the leading + is stripped automatically); otherwise the customer enters it on Any.Money's hosted page.
customer.email is optional and, when sent, is forwarded to Any.Money as the client's email.
Only the RUB QIWI service is available on the Provider account for Payments.

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

Refunds

Any.Money does not support refunds on the Provider account.

Payouts processing (connect Provider account, create payout-invoice)

Connect Provider account in Corefy Dashboard

Payouts use the same Provider account connection described above - no separate connection is needed if you already connected it for Payments.

First request to Corefy API (MIN)

What it does: creates a payout-invoice. The required fields key depends on the payout method and currency (see the table below).

Payout - MIN

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "5e6f7a8b-9c0d-4e1f-9024-4a5b6c7d8e9f",
      "service": "payment_card_uah",
      "currency": "UAH",
      "amount": 100,
      "fields": {
        "card_number": "4111111111111111"
      }
    }
  }
}

Payout - MAX

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "6f7a8b9c-0d1e-4f20-9135-5a6b7c8d9e0f",
      "service": "bank_transfer_uah",
      "currency": "UAH",
      "amount": 100,
      "fields": {
        "account_number": "UA123456789012345678901234567",
        "individual_tax_number": "1234567890",
        "recipient_name": "Ivanov Ivan",
        "sender_name": "Petrov Petro"
      }
    }
  }
}

Important

Each payout method expects a different fields key for the recipient identifier - sending the wrong one for the chosen service causes the request to fail:

Payout method	Currencies	`fields` key(s)
Card	UAH, KZT, USD, RUB	`card_number`
Mobile	UAH, RUB	`phone`
QIWI wallet	RUB	`phone` (the leading `+` is stripped automatically)
Bitcoin	BTC	`wallet_id`
Litecoin	LTC	`wallet_id`
Ethereum	ETH	`wallet_id`
Bitcoin Cash	BCH	`wallet_id`
Tether	USD	`wallet_id`
Bank transfer	UAH, EUR	`account_number`, `individual_tax_number`, `recipient_name`, `sender_name`

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

Any.Money does not support refunds for payouts.

Additional info

Callback routing is automatic on the H2H Merchant account - Corefy generates the callback/return URLs per transaction, nothing to configure in Any.Money's own back-office.
Available payout routes are auto-discovered - Corefy cross-references the methods/currencies above against Any.Money's own live payways list for your account, so a method may be unavailable if Any.Money hasn't enabled it for your merchant yet.
No recurring - this connector does not support saving/charging a token through Corefy.

FAQ / Troubleshooting

Invalid credentials / auth error -> verify the merchant ID, signature key and fee strategy for the selected account type and environment (test_mode) - H2H Merchant account and Provider account use entirely different credential sets
Payout fails with an unsupported method error -> check that the service/currency pair is listed in the table above, and that Any.Money has enabled that route for your merchant
Currency or service is not supported -> confirm allowed currencies/features in your Any.Money account and in Corefy
Not sure which account type to use? -> H2H Merchant account is for card Payments; Provider account is for QIWI Payments and all Payouts

Question

Still looking for help connecting your Any.Money account? Please contact our support team!