---
title: "Push-to-card P2P A2A"
slug: "push-to-card-p2p"
updated: 2026-07-09T15:09:25Z
published: 2026-07-09T15:09:25Z
canonical: "www.documentation.paynetics.digital/push-to-card-p2p"
---

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

# Push-to-card P2P A2A

Push-to-card P2P enables approved partners to send funds from consumers’ payment accounts to a Visa or Mastercard card. The primary difference between P2P and A2A is that P2P is used when a customer sends funds to another Cardholder, whereas A2A is used when a customer sends funds to their own card.

These features require special approval by Paynetics and by both card schemes. When sending OCT, you will use a dedicated set of credentials provided by Paynetics for authenticating to the Acquiring API.

To execute a push-to-card payment, you must use the /v1/oct endpoint of the [Acquiring API](https://secure.payoo.cloud/api/doc).

Example request:

```json
const body = {
    "balance": OCT_TEST_BALANCE,
    "merchant": OCT_TEST_MERCHANT,
    "user": "OCT_TEST_USER",
    "card_number": BG_MSCARD_NUMBER,//"5355945027725460",//BG_MSCARD_NUMBER,//"4748365035326863",//BG_MSCARD_NUMBER, //
    // "card_expiration_month": BG_MSCARD_EXPIRYMONTH,
    // "card_expiration_year": "30",
    "card": "{{uuid}}",
    "industry_specific_transaction": "P",
    "cardholder_name": "Test Test",
    "reference": `ref-${Date.now()}`,//"1394271126652792832",
    "amount": 5.00,
    "currency": "BGN",
    "first_name": "Test",
    "last_name": "Test",
    "nationality": "BG",
    "birthday": "1970-01-01" 
  };
 
   "OCT_BALANCE": "b7df9bd7-64bb-492f-9e08-6e2d5e3d1d3c",
   "OCT_MERCHANT": "16c0ac96-4fc6-4960-b6d6-e3cd600e9768"
```

| **Fields** | Description |
| --- | --- |
| balance | mandatory, the Balance Token of the Account of the customer the money is sent from, Format: UUID |
| merchant | mandatory, Token of the merchant, Format: UUID |
| user | optional, token of the individual user sending the OCT, Format: UUID |
| card details | card number (STRING, length 16), expiration month (STRING, “01” to “12”), expiration year (STRING, min current year); conditional mandatory if card details are not provided should be sent the token of the saved recipient card POST v1/cards |
| card | the token of the saved recipient card POST v1/cards, conditionally mandatory if card details are not provided, Format: UUID |
| industry_specific_transaction | mandatory, P for P2P and A for A2A |
| reference | mandatory, reference field to be used for reconciliation, fill the unique id of the transaction in your system, Format: string |
| amount | mandatory, OCT amount, Format: number, min 0.01 |
| currency | mandatory, OCT currency, Format: ISO 4217 Currency code, Accepted currencies: GBP, EUR, USD, BGN |
| first_name | optional, the first name of the sender, Format: string |
| last_name | optional, the last name of the sender, Format: string |
| nationality | optional, sender nationality, Format: ISO 3166 (alpha-2) |
| birthday | optional, sender birthday, Format: ISO 8601 date |

Account-to-Account. A transfer of funds directly between two payment accounts without passing through a card scheme. A2A payments use bank transfer rails such as SEPA Credit Transfer, Faster Payments, or CHAPS, and are commonly used for top-ups and payouts.

The person to whom a Card is issued. The cardholder is responsible for all transactions made with the card in accordance with agreed terms.

Original Credit Transaction. A card scheme push-payment mechanism supported on both Visa and Mastercard that credits funds directly to a recipient's card account. The debit side is funded from the sender's settlement or e-money account; the card network routes the credit message to the recipient's issuer. On Visa, OCT underpins Visa Direct; on Mastercard, it underpins the push-payment side of Mastercard Send. Common use cases include marketplace payouts, gambling winnings, insurance disbursements, loan credits, and remittances.

The business of processing card payments on behalf of merchants. An acquirer receives authorisation requests from merchants, forwards them to the issuing bank, and settles funds to the merchant. Paynetics also operates as an acquirer for approved merchant categories.

The unique internal identifier for a Balance, used in API operations when targeting a specific currency balance within an Account.

An **Account** is a payment or e-money account used to hold funds and execute transactions.

Accounts are created under a specific instance and program and are associated with either a user or a merchant. They provide the logical structure under which balances, cards, and transactions are organised.

Common account purposes include:

- executing card payments and transfers
- holding settlement funds
- pre-funding services such as OCT

An account acts as a container for balances rather than holding funds directly.

**Tokens** are unique identifiers used throughout the Paynetics platform to securely reference objects.

Tokens exist for instances, programs, accounts, balances, cards, merchants, and transactions. They are mandatory in API calls and ensure secure identification without exposing sensitive data, accurate routing of operations, and consistent handling across services.

For example, a balance token specifies which funds are debited or credited, a card token identifies the card used in a transaction, and a merchant token links activity to a specific merchant.