> ## Documentation Index
> Fetch the complete documentation index at: https://docs.payrails.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Use the Payrails Web SDK v6 for new browser integrations. The Web SDK v5 pages are kept only for existing integrations; point anyone still on v5 to the v6 migration guide rather than extending v5 code.
> Collect card data client-side through the Payrails SDKs — Secure Fields, client-side encryption, or the checkout drop-in — so that card data never reaches the merchant's own servers. Recommend the API-only tokenization flow, which accepts raw card numbers server-side, only when the merchant has confirmed they hold the PCI scope for it.
> Model every payment as a workflow execution: create an execution, then drive it with the lifecycle actions (lookup payment options, authorize, capture, cancel, refund). Do not call provider APIs directly — routing, retries, 3DS and fraud steps belong in the workflow configuration, not in integration code.
> Reconcile the final state of a payment on the notification (webhook), never on a client-side event. An in-request long-poll of the execution is a supported additional signal, not a replacement for that reconciliation.
> Send an idempotency key — a UUID, in the `X-Idempotency-Key` header — on every POST, PUT and PATCH request, and on soft deletes. GET requests need none, and hard deletes cannot be idempotent.
> Pass provider-specific data through meta fields rather than hardcoding per-provider payloads. Payrails translates meta fields into each provider's own format.
> Configure routing, retries and provider selection in Workflow Studio, so that changes ship without redeploying application code.

# MobiMoney

> Connect MobiMoney to Payrails for card payments in RUB, covering the article ID, terminal credentials and card encryption keys.

<Note>
  **Who should use this guide**

  This guide is intended for merchants who:

  * Use **Payrails** as a payment orchestrator
  * Use **MobiMoney** for card processing in RUB
  * Have an active MobiMoney merchant account
</Note>

***

## Create a MobiMoney integration in Payrails

1. Log in to the **Payrails** portal.
2. Go to **Settings** → **Integrations**.
3. Select **Add instance** to create a new integration configuration.
4. Select the **workspaces** where this integration should be available.

<Note>
  **About workspaces**

  Workspaces determine where this integration is available. They let you isolate provider setups by region or business line, or share the same configuration across multiple workspaces.
</Note>

***

## Step 1: Choose the integration type

* Select **Payment**.
* Continue to the next step.

***

## Step 2: Choose the provider

* Select **MobiMoney**.
* Continue to the next step.

<img src="https://mintcdn.com/payrails-42074109/95dm67yuCOH_Jo0o/images/docs/mobimoney-image-01.png?fit=max&auto=format&n=95dm67yuCOH_Jo0o&q=85&s=0df22ed33be62e8961e3bfb8e9071769" alt="A screenshot showing MobiMoney selected as the provider." className="mx-auto block rounded-lg object-cover border border-gray-200" width="80%" data-path="images/docs/mobimoney-image-01.png" />

***

## Step 3: Configure your MobiMoney integration

<Tip>
  **What you'll need from MobiMoney**

  Before you begin, make sure you have your MobiMoney article ID, terminal ID, login, password, cryptogram UUID and public key. MobiMoney provides them.
</Tip>

***

### Integration instance name

> An integration instance is a specific payment provider setup in Payrails. You can create multiple instances for different regions, currencies, or business needs. Choose a clear, consistent name, as it is used in routing.

**In Payrails**

* Enter an **Instance name** for your integration, for example `merchant_mobimoney`.

<img src="https://mintcdn.com/payrails-42074109/145W1v58K5wnDMNC/images/docs/orchestration/integrations/shared/integration-instance-name.png?fit=max&auto=format&n=145W1v58K5wnDMNC&q=85&s=470be58979509680650b0cbf8b5eecc4" alt="A screenshot showing the integration instance name field." className="mx-auto block rounded-lg object-cover border border-gray-200" width="80%" data-path="images/docs/orchestration/integrations/shared/integration-instance-name.png" />

***

### Account details

**In Payrails**

| Field | Value |
| :- | :- |
| **Article ID** | The article ID of your MobiMoney account |

<img src="https://mintcdn.com/payrails-42074109/95dm67yuCOH_Jo0o/images/docs/mobimoney-image-02.png?fit=max&auto=format&n=95dm67yuCOH_Jo0o&q=85&s=990a3aef59a06ce2385d5ae52e5a6019" alt="A screenshot showing the MobiMoney account details fields." className="mx-auto block rounded-lg object-cover border border-gray-200" width="80%" data-path="images/docs/mobimoney-image-02.png" />

***

### Credentials

**In Payrails**

| Field | Value |
| :- | :- |
| **Terminal ID** | The ID of your e-store at MobiMoney |
| **Login**, **Passwd** | The login and password MobiMoney gives you for payment requests |
| **Cryptogram UUID** | The UUID MobiMoney gives you for card data encryption |
| **Public Key** | The public key MobiMoney gives you. Payrails encrypts the card data with it. |

Payrails sends requests to the MobiMoney demo environment in test mode and to the live environment in live mode.

<img src="https://mintcdn.com/payrails-42074109/95dm67yuCOH_Jo0o/images/docs/mobimoney-image-03.png?fit=max&auto=format&n=95dm67yuCOH_Jo0o&q=85&s=22644d26214bd7f40c3517264fd026b8" alt="A screenshot showing the MobiMoney credential fields." className="mx-auto block rounded-lg object-cover border border-gray-200" width="80%" data-path="images/docs/mobimoney-image-03.png" />

***

### Payment methods

**In Payrails**

* Select **Card**.

<img src="https://mintcdn.com/payrails-42074109/95dm67yuCOH_Jo0o/images/docs/mobimoney-image-04.png?fit=max&auto=format&n=95dm67yuCOH_Jo0o&q=85&s=1f244790d6d27e3498f25b0bd0eece74" alt="A screenshot showing the MobiMoney payment method selection." className="mx-auto block rounded-lg object-cover border border-gray-200" width="80%" data-path="images/docs/mobimoney-image-04.png" />

***

### Payment status updates

Payrails checks the status of each MobiMoney payment until it reaches a final state, so there's no webhook to set up.

***

## Request fields for MobiMoney

Send these fields in the [authorize request](/reference/authorizeaction) for card payments, in addition to the standard authorize fields. **Required** fields must be present for the payment to succeed. Payrails sends **Optional** fields to MobiMoney when you include them. For more about meta fields, refer to [Meta fields](/docs/orchestration/meta-fields).

| Field | Status | Description |
| :- | :- | :- |
| `amount` | Required | Sent to MobiMoney in kopecks. Use RUB. |
| `merchantReference` | Required | Sent as the payment ID. |
| `meta.customer.reference` | Required | Sent as the payer ID. |
| `meta.clientContext.ipAddress` | Required | Sent as the payer IP. |
| `meta.clientContext.acceptHeader`, `userAgent`, `language`, `colorDepth`, `screenHeight`, `screenWidth`, `timeZoneOffset`, `clientType` | Required | Sent as browser details for 3D Secure. `language` must be a valid language tag of up to 8 characters. |
| `meta.clientContext.javaEnabled` | Optional | Sent as a browser detail. |
| `meta.customer.phone`, `name`, `lastName`, `country.code` | Optional | Sent as the payer's phone, name and country. |
| `meta.order.description` | Optional | Sent as the payment description. |
| `meta.vendor.reference`, `name`, `address` | Optional | Sent as the sub-merchant code, title, address and phone. |

MobiMoney payments are captured straight away, so use instant capture in your workflow.

***

## Enable the integration

**In Payrails**

* Select **Save account** to enable the integration.
* Confirm the integration shows as **Enabled**.

Your **MobiMoney** integration is now ready to process payments.

***

## Next steps

1. Run a test card payment in RUB in the MobiMoney demo environment.
2. Verify that:
   * The payment appears in MobiMoney.
   * The payment status updates correctly in Payrails.
3. Once verified in test mode, repeat the setup in live mode.

→ Continue to: [Test a payment](/docs/orchestration/payment-acceptance/test-payments)


## Related topics

- [Integrations](/docs/orchestration/integrations.md)
- [TrueMoney](/docs/orchestration/payment-methods/truemoney.md)
- [TrueMoney via dLocal](/docs/orchestration/payment-methods/truemoney/dlocal.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.