Any.Cash
Convenient and secure digital wallet on Telegram
Supports in this guide: Payments, Payouts
Provider website: any.cash
What you need to do for start processing transactions (brief summary)
- Get your credentials (from Any.Cash)
- Connect in Dashboard
- Send an API request
Prerequisites: get from Any.Cash
Contact your Any.Cash manager to create a wallet (via the @AnyCashBot Telegram bot or the Create Wallet button on their site) and get your account verified. Payments and Payouts share the same Provider account credentials:
- Merchant ID -> Corefy field
merchant. - Signature key -> Corefy field
signature_key.
Note
If you need to whitelist IPs on Any.Cash's side, ask your account manager and provide Corefy's IP list from the integration docs.
Payments processing (connect Provider account, create payment-invoice)
Connect Provider account in Corefy Dashboard
Step 1 - Open connection form
Open Any.Cash in the provider directory and press Connect at Any.Cash Provider Overview page in the New connection section.
Step 2 - Fill in fields and select settings
- Merchant ID
- Signature key
- Currency / Features -> choose values available for your account (crypto: BTC, BCH, LTC, ETH, USDT; QIWI: RUB)
Success
You have connected Any.Cash Provider account!
First request to Corefy API (MIN)
What it does: creates a payment-invoice and redirects the customer to Any.Cash's own hosted payment page (SCI) to complete the payment.
Payment - MIN
POST /api/payment-invoices
{
"data": {
"type": "payment-invoice",
"attributes": {
"reference_id": "1a2b3c4d-5e6f-4a7b-8c91-2d3e4f5a6b7c",
"service": "bitcoin_btc",
"currency": "BTC",
"amount": 0.001
}
}
}
Payment - MAX (QIWI)
POST /api/payment-invoices
{
"data": {
"type": "payment-invoice",
"attributes": {
"reference_id": "2b3c4d5e-6f7a-4b8c-8d02-3e4f5a6b7c8d",
"service": "qiwi_rub",
"currency": "RUB",
"amount": 500,
"fields": {
"phone": "+79991234567"
}
}
}
}
Important
fields.phone is required only for the qiwi_rub service - it is the customer's QIWI wallet phone number (the leading + is stripped automatically). It is not used for the crypto services.
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
Available services (service -> currency)
bitcoin_btc->BTCbitcoin_cash_bch->BCHlitecoin_ltc->LTCethereum_eth->ETHtether_usd->USD(USDT)qiwi_rub->RUB
This connector has no Options or Constants: card/crypto/wallet fields are either passed directly in the request fields, as shown above, or not required at all.
Refunds
Any.Cash does not support refunds.
Payouts processing (connect Provider account, create payout-invoice)
Connect Provider account in Corefy Dashboard
Uses the same Provider account connected above - no separate connection is needed for Payouts.
First request to Corefy API (MIN)
What it does: creates a payout-invoice and sends funds to a wallet or card, depending on the service.
Payout - MIN (crypto/QIWI/WebMoney)
POST /api/payout-invoices
{
"data": {
"type": "payout-invoice",
"attributes": {
"reference_id": "3c4d5e6f-7a8b-4c9d-8e02-3f4a5b6c7d8e",
"service": "bitcoin_btc",
"currency": "BTC",
"amount": 0.001,
"fields": {
"wallet_id": "1A2b3C4d5E6f7G8h9I0jK1l2M3n4O5p6Q7"
}
}
}
}
Important
fields.wallet_id is required for all crypto, QIWI, and WebMoney Transfer services - it accepts the recipient's wallet address, QIWI phone number (+ is stripped automatically), or WebMoney purse, depending on the service.
Payout - MIN (card)
POST /api/payout-invoices
{
"data": {
"type": "payout-invoice",
"attributes": {
"reference_id": "4d5e6f7a-8b9c-4d0e-8f13-4a5b6c7d8e9f",
"service": "payment_card_uah",
"currency": "UAH",
"amount": 500,
"fields": {
"card_number": "4111111111111111"
}
}
}
}
Important
fields.card_number is required for payment_card_rub and payment_card_uah.
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
Available services (service -> currency -> required field)
bitcoin_btc->BTC->fields.wallet_idbitcoin_cash_bch->BCH->fields.wallet_idlitecoin_ltc->LTC->fields.wallet_idethereum_eth->ETH->fields.wallet_idtether_usd->USD(USDT) ->fields.wallet_idqiwi_rub->RUB->fields.wallet_id(QIWI phone number)webmoneytransfer_rub->RUB->fields.wallet_idwebmoneytransfer_usd->USD->fields.wallet_idpayment_card_rub->RUB->fields.card_numberpayment_card_uah->UAH->fields.card_number
This connector has no Options or Constants, and does not support refunds (payouts generally cannot be refunded on this platform).
Additional info
- Payments are hosted (SCI) - the customer is redirected to Any.Cash's own hosted payment page to complete the transaction; Corefy does not collect card/wallet data for Payments itself.
- Callback and active reconciliation are both available - Payments support an asynchronous callback (HMAC-SHA512 signed) and an active status request; Payouts support an asynchronous callback and reconciliation too.
- No recurring - this connector does not support saving/charging a token through Corefy.
FAQ / Troubleshooting
- Invalid signature / auth error -> verify the Merchant ID and Signature key match what Any.Cash issued
- Payment fails on QIWI -> make sure
fields.phoneis sent in the international format (the connector strips the leading+automatically) - Payout fails with an invalid destination error -> verify
fields.wallet_id(orfields.card_numberfor card payouts) matches the format expected by the selected service - Currency or service is not supported -> confirm allowed currencies/services in your Any.Cash account and in Corefy
Question
Still looking for help connecting your Any.Cash account? Please contact our support team!