131.ru valid
Bank 131 API
Bank 131 API provides everything you need for payments, payouts, and settlement between people and companies online. Base URL: `https://demo.bank131.ru` (demo) / `https://proxy.bank131.ru` (live). Sign every request body with RSA-SHA256 and send Base64 signature in `X-PARTNER-SIGN` header. Include `X-PARTNER-PROJECT` in every request.
For agents: Bank 131 API docs for payments, payouts and settlement between people and companies; RSA-SHA256 signed requests, demo and live environments.
payments apipayoutssettlementrsa signaturebank 131
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-23T13:28:46.964Z. Cached copy · Source on 131.ru
# Bank 131 API
> Bank 131 API provides everything you need for payments, payouts, and settlement between people and companies online. Base URL: `https://demo.bank131.ru` (demo) / `https://proxy.bank131.ru` (live). Sign every request body with RSA-SHA256 and send Base64 signature in `X-PARTNER-SIGN` header. Include `X-PARTNER-PROJECT` in every request.
## Getting Started
- [Bank 131 API](https://developer.131.ru/en/): API for Internet platforms offering various online services
- [API features](https://developer.131.ru/en/intro): API for Internet platforms providing various online services
- [Where to begin](https://developer.131.ru/en/before): How to test and perform real operations
- [Which account type to choose](https://developer.131.ru/en/account-selection): Choose an account type by goal—payment acceptance and payouts
- [API request format](https://developer.131.ru/en/reference/format): All about working with Bank 131 API
- [API testing](https://developer.131.ru/en/reference/testing): Data for test operations
- [Standard payout and payment scenarios](https://developer.131.ru/en/reference/typical): Standard payout and payment scenarios
- [Configuring trust for certificates of the Russian Ministry of Digital Development for working with Bank 131 services](https://developer.131.ru/en/reference/certificates): Installation of Russian Ministry of Digital Development certificates
## Payouts
- [Collateral account API](https://developer.131.ru/en/payouts/collateral-intro): Details on operations with a collateral account in Bank 131
- [Monthly reports](https://developer.131.ru/en/payouts/finance-act): Via email, EDM, or on paper
- [Speedy payouts to accounts via BESP](https://developer.131.ru/en/payouts/payout-account-sistema-besp): Speedy payouts to accounts via BESP
- [Payouts to cards in a foreign currency](https://developer.131.ru/en/payouts/payout-currency): Payouts in a foreign currency
- [Payouts via FPS to a phone number](https://developer.131.ru/en/payouts/payout-fps-phone): Payouts to individuals' accounts via FPS
- [About payouts](https://developer.131.ru/en/payouts/payouts-intro): API for convenient and secure payouts
- [Payouts by card number](https://developer.131.ru/en/payouts/payout-pcidss): Payouts by card number
- [Refunds of payouts made to accounts](https://developer.131.ru/en/payouts/payout-refunds): Checking the payouts status
- [Parameters for payouts to Russian bank accounts](https://developer.131.ru/en/payouts/russian-account-parameters): Payouts to the self-employed, sole entrepreneurs, legal entities, and individuals
- [Payouts by bank account number](https://developer.131.ru/en/payouts/russian-account): Payouts by bank account number
- [Payout parameters for Russian bank cards](https://developer.131.ru/en/payouts/russian-card): Payouts by Visa, MasterCard, and Mir
- [Main payout scenario](https://developer.131.ru/en/payouts/payout-scenarios): Payouts via API with and without a token
- [Payouts to the Russian Federal Tax
…
Related sites
Find similar publishers by meaning →
Other listed sites in Finance and payments. See the whole category →
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| forter.com | Forter — Identity Intelligence for Digital Commerce | interface Ecommerce Cybersecurity +1 | US | 75 | ✓ | ✓ | |
| paypal.com | PayPal | transactional Finance and payments | — | 73 | ✓ | ||
| stripe.com | Stripe | interface Finance and payments APIs and SDKs | IE | 72 | ✓ | ||
| coinmarketcap.com | CoinMarketCap API Documentation | interface Developer tools APIs and SDKs +2 | — | 71 | ✓ | ✓ | |
| opentext.com | OpenText | documentation Cybersecurity Finance and payments +4 | CA | 70 | ✓ | ✓ | |
| square.site | Square (US - English) | transactional Ecommerce Finance and payments | US | 69 | ✓ | ||
| clerk.com | Clerk | interface Finance and payments Authentication and identity +1 | US | 68 | ✓ | ✓ | |
| solana.com | Solana Documentation | documentation Finance and payments Documentation and reference +2 | US | 68 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=131.ru · GET /v1/domain/131.ru · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage 131.ru, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for 131.ru:
1. POST https://agentwebmap.com/v1/sites/131.ru/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://131.ru/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/131.ru/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/131.ru).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.