Skip to main content

P2P Card Credit

POST 

https://pay.fondy.eu/api/p2pcredit

This endpoint allows a merchant to perform a peer-to-peer (P2P) card credit transaction, transferring funds directly to a recipient's card number or a stored receiver token. The request must include either receiver_card_number or receiver_rectoken, along with transaction details such as order_id, order_desc, and amount.

To secure this request, the merchant must generate a signature using their Credit private key specifically for p2pcredit operations.

Request

Header Parameters

    Content-Type stringrequired

    Possible values: [application/json, application/xml, application/x-www-form-urlencoded]

    Specifies the format for the request. Response will be in the same format.

    Default value: application/json

Body

    request object
    merchant_idinteger

    A unique identifier assigned to the merchant by Fondy. Required to authenticate and associate the transaction with the merchant’s account.

    Example: 1396424
    order_idstring

    A unique order reference defined by the merchant. Used to identify the transaction throughout its lifecycle.

    Example: besh_p2p_1743690601
    amountinteger

    Total transaction amount in minor currency units (e.g., cents). For example, 10000 in USD represents $100.00.

    Example: 10000
    currencystring

    Currency in which the transaction is processed, using the ISO 4217 format (e.g., USD, EUR).

    Example: USD
    order_descstring

    A brief UTF-8 description of the transaction. This will be visible in reports and payment records.

    Example: Fondy P2P Card Credit Payment via Python API
    receiver_card_numberstringrequired

    The recipient’s full card number to which funds will be credited. Must be a valid Visa or Mastercard.

    Example: 4444555566661111
    signaturestring

    A hash signature generated using Fondy’s signature algorithm to verify the authenticity and integrity of the request.

    Example: 19059322c0efdfd445d38c2ac19034cfd926151d

Responses

The response for a successful transaction.

Schema
    response object

    Parameters of the final response

    order_idOrderId (string)

    A unique identifier for the order. This can be any value defined by the merchant, allowing you to use any internal order identification system your business employs.

    Example: ORDER_12345678
    merchant_idMerchantId (integer)

    A unique identifier assigned to the merchant by Fondy upon account registration. This ID is required for authenticating requests and associating transactions with the merchant's account.

    Possible values: <= 12 characters

    Example: 1
    amountinteger

    Order amount in cents without separator.

    Possible values: <= 12 characters

    currencyCurrency (string)

    Currency for the transaction (e.g., GBP, EUR, USD). Refer to the Currencies page for a full list of available currencies.

    Possible values: <= 3 characters, [AED, AFN, ALL, AMD, ANG, AOA, ARS, AUD, AWG, AZN, BAM, BBD, BDT, BGN, BHD, BIF, BMD, BND, BOB, BRL, BSD, BTN, BWP, BZD, CAD, CDF, CHF, CLP, CNY, COP, CRC, CUP, CVE, CZK, DJF, DKK, DOP, DZD, EGP, ERN, ETB, EUR, FJD, FKP, GBP, GEL, GHS, GIP, GMD, GNF, GTQ, GYD, HKD, HNL, HRK, HTG, HUF, IDR, ILS, INR, IQD, IRR, ISK, JMD, JOD, JPY, KES, KGS, KHR, KMF, KRW, KWD, KYD, KZT, LAK, LBP, LKR, LRD, LSL, LTL, LVL, LYD, MAD, MDL, MGA, MKD, MMK, MNT, MOP, MUR, MVR, MWK, MXN, MYR, MZN, NAD, NGN, NIO, NOK, NPR, NZD, OMR, PAB, PEN, PGK, PHP, PKR, PLN, PYG, QAR, RON, RSD, RWF, SAR, SBD, SCR, SDG, SEK, SGD, SHP, SLL, SOS, SRD, STD, SVC, SZL, THB, TJS, TMT, TND, TOP, TRY, TTD, TWD, TZS, UAH, UGX, USD, UYU, UZS, VEF, VND, VUV, WST, XAF, XCD, XOF, XPF, YER, ZAR, ZMW, ZWD]

    order_statusstring

    Order processing status indicating the current state of the transaction.

    Enum ValueDescription
    createdOrder has been created, but the customer has not entered payment details yet; the merchant should continue to request the status of the order.
    processingOrder is still processing by the payment gateway; the merchant should continue to request the status of the order.
    declinedOrder is declined by Fondy, a bank, or an external payment system.
    approvedOrder completed successfully, funds are held on the payer’s account and soon will be credited to the merchant; the merchant can provide the service or ship goods.
    expiredOrder lifetime expired.
    reversedPreviously approved transaction was fully reversed. In this case, the reversal_amount will equal actual_amount.

    Possible values: <= 50 characters, [created, processing, declined, approved, expired, reversed]

    response_statusstring

    Request processing status (e.g., 'success' or 'failure').

    Possible values: <= 50 characters

    signaturestring

    Order signature for request verification.

    Possible values: <= 40 characters

    tran_typestring

    Possible values: <= 50 characters, [purchase, verification, p2p credit, p2p transfer, settlement, reverse]

    sender_cell_phonestring

    Customer's mobile phone number.

    Possible values: <= 16 characters

    sender_accountstring

    Customer payment account.

    Possible values: <= 50 characters

    masked_cardstring

    Masked card number.

    Possible values: <= 19 characters

    card_bininteger

    First 6 digits of the card number.

    Possible values: <= 6 characters

    card_typestring

    Possible values: <= 50 characters, [VISA, MasterCard]

    rrnstring

    Bank transaction ID, often not unique.

    Possible values: <= 50 characters

    approval_codestring

    Authorisation code returned by the bank.

    Possible values: <= 6 characters

    response_codeinteger

    Order decline response code.

    Possible values: <= 4 characters

    response_descriptionstring

    Description of the response code.

    Possible values: <= 1024 characters

    reversal_amountinteger

    Total reversal amount for the current order.

    Possible values: <= 12 characters

    settlement_amountinteger

    Settlement amount for the current order.

    Possible values: <= 12 characters

    settlement_currencyCurrency (string)

    Currency for the transaction (e.g., GBP, EUR, USD). Refer to the Currencies page for a full list of available currencies.

    Possible values: <= 3 characters, [AED, AFN, ALL, AMD, ANG, AOA, ARS, AUD, AWG, AZN, BAM, BBD, BDT, BGN, BHD, BIF, BMD, BND, BOB, BRL, BSD, BTN, BWP, BZD, CAD, CDF, CHF, CLP, CNY, COP, CRC, CUP, CVE, CZK, DJF, DKK, DOP, DZD, EGP, ERN, ETB, EUR, FJD, FKP, GBP, GEL, GHS, GIP, GMD, GNF, GTQ, GYD, HKD, HNL, HRK, HTG, HUF, IDR, ILS, INR, IQD, IRR, ISK, JMD, JOD, JPY, KES, KGS, KHR, KMF, KRW, KWD, KYD, KZT, LAK, LBP, LKR, LRD, LSL, LTL, LVL, LYD, MAD, MDL, MGA, MKD, MMK, MNT, MOP, MUR, MVR, MWK, MXN, MYR, MZN, NAD, NGN, NIO, NOK, NPR, NZD, OMR, PAB, PEN, PGK, PHP, PKR, PLN, PYG, QAR, RON, RSD, RWF, SAR, SBD, SCR, SDG, SEK, SGD, SHP, SLL, SOS, SRD, STD, SVC, SZL, THB, TJS, TMT, TND, TOP, TRY, TTD, TWD, TZS, UAH, UGX, USD, UYU, UZS, VEF, VND, VUV, WST, XAF, XCD, XOF, XPF, YER, ZAR, ZMW, ZWD]

    order_timedate-time

    Order creation date in DD.MM.YYYY hh:mm:ss format.

    settlement_datedate

    Settlement date in DD.MM.YYYY format.

    eciinteger

    Ecommerce Indicator for 3DSecure authentication status.

    Possible values: <= 2 characters, [5, 6, 7]

    feeinteger

    Fee charged by Fondy.

    Possible values: <= 12 characters

    payment_systemstring

    Payment system used for the transaction.

    Possible values: <= 50 characters

    sender_emailSenderEmail (string)

    Your customer's email address. Fondy will send an email regarding the payment to this address.

    Possible values: <= 254 characters

    payment_idinteger

    Unique payment ID generated by Fondy.

    Possible values: <= 19 characters

    actual_amountinteger

    Actual amount held or charged from the card.

    Possible values: <= 12 characters

    actual_currencyCurrency (string)

    Currency for the transaction (e.g., GBP, EUR, USD). Refer to the Currencies page for a full list of available currencies.

    Possible values: <= 3 characters, [AED, AFN, ALL, AMD, ANG, AOA, ARS, AUD, AWG, AZN, BAM, BBD, BDT, BGN, BHD, BIF, BMD, BND, BOB, BRL, BSD, BTN, BWP, BZD, CAD, CDF, CHF, CLP, CNY, COP, CRC, CUP, CVE, CZK, DJF, DKK, DOP, DZD, EGP, ERN, ETB, EUR, FJD, FKP, GBP, GEL, GHS, GIP, GMD, GNF, GTQ, GYD, HKD, HNL, HRK, HTG, HUF, IDR, ILS, INR, IQD, IRR, ISK, JMD, JOD, JPY, KES, KGS, KHR, KMF, KRW, KWD, KYD, KZT, LAK, LBP, LKR, LRD, LSL, LTL, LVL, LYD, MAD, MDL, MGA, MKD, MMK, MNT, MOP, MUR, MVR, MWK, MXN, MYR, MZN, NAD, NGN, NIO, NOK, NPR, NZD, OMR, PAB, PEN, PGK, PHP, PKR, PLN, PYG, QAR, RON, RSD, RWF, SAR, SBD, SCR, SDG, SEK, SGD, SHP, SLL, SOS, SRD, STD, SVC, SZL, THB, TJS, TMT, TND, TOP, TRY, TTD, TWD, TZS, UAH, UGX, USD, UYU, UZS, VEF, VND, VUV, WST, XAF, XCD, XOF, XPF, YER, ZAR, ZMW, ZWD]

    product_idstring

    Merchant's product or service ID.

    Possible values: <= 1024 characters

    merchant_dataMerchantData (string)

    Custom data provided by the merchant in the request. You can include any arbitrary string data relevant to your business needs, such as user IDs, session information, or notes. The data must be in string format and must not contain the '|' (pipe) character.

    Possible values: <= 2048 characters

    verification_statusstring

    Code verification result.

    Possible values: <= 50 characters, [verified, incorrect, failed, created]

    rectokenstring

    Token for accessing card funds without cardholder interaction.

    Possible values: <= 40 characters

    rectoken_lifetimedate-time

    Token expiration date in DD.MM.YYYY hh:mm:ss format.

    additional_info object

    Additional information in JSON format.

    bank_namestring

    Bank name.

    bank_countrystring

    Bank country.

    bank_response_codestring

    Response code from the bank.

    card_productstring

    Type of card product.

    card_categorystring

    Category of the card.

    settlement_feenumber

    Settlement fee.

    capture_statusstring

    Status of the capture.

    client_feenumber

    Fee charged to the client.

    ipaddress_v4string

    IP address in IPv4 format.

    capture_amountinteger

    Amount captured.

    card_typestring

    Type of the card used.

    Possible values: [VISA, MasterCard]

    reservation_datastring

    Reservation data.

    bank_response_descriptionstring

    Description of the bank's response.

    transaction_idinteger

    Transaction ID from the bank.

    timeenddate-time

    End time for the transaction.

    card_numberstring

    Card number used.

    payment_methodstring

    Payment method used.

    Possible values: [apple, googlepay, card]

var client = new HttpClient();
var request = new HttpRequestMessage(HttpMethod.Post, "https://pay.fondy.eu/api/p2pcredit");
request.Headers.Add("Accept", "application/json");
var content = new StringContent("{\n \"request\": {\n \"merchant_id\": 1396424,\n \"order_id\": \"besh_p2p_1743690601\",\n \"amount\": 10000,\n \"currency\": \"USD\",\n \"order_desc\": \"Fondy P2P Card Credit Payment via Python API\",\n \"receiver_card_number\": 4444555566661111,\n \"signature\": \"19059322c0efdfd445d38c2ac19034cfd926151d\"\n }\n}", null, "application/json");
request.Content = content;
var response = await client.SendAsync(request);
response.EnsureSuccessStatusCode();
Console.WriteLine(await response.Content.ReadAsStringAsync());
Request Collapse all
Base URL
https://pay.fondy.eu/api
Parameters
— headerrequired
Body
{
  "request": {
    "merchant_id": 1396424,
    "order_id": "besh_p2p_1743690601",
    "amount": 10000,
    "currency": "USD",
    "order_desc": "Fondy P2P Card Credit Payment via Python API",
    "receiver_card_number": 4444555566661111,
    "signature": "19059322c0efdfd445d38c2ac19034cfd926151d"
  }
}
ResponseClear

Click the Send API Request button above and see the response here!