Skip to main content

[PayIn] ARS Payment Data

For shops with ARS currency, when creating a payin (POST /api/v1/payins), no additional fields are required in the paymentData object.

Required fields in paymentData

No additional paymentData fields are required for ARS payins.

Example request body

{
"external_id": "PIN-ARS-001",
"amount": 5000.00,
"currency": "ARS",
"shop_code": "your_ars_shop"
}

Response fields

ParameterTypeDescription
idnumberTrustedPay operation ID.
statusstringCurrent payin status.
external_idstringUnique payin identifier from the request.
amountnumberPayin amount.
currencystringPayin currency.
shop_codestringShop code used for routing.
payment_page_urlstringURL of the hosted payment page.
payment_page_expires_atstringHosted payment page expiration timestamp.
transaction_typestringAlways payin.
created_atstringCreation timestamp.
updated_atstringLast update timestamp.
finalization_datestringReturned when the payin reaches a final status.

Example response body

{
"id": 12345,
"status": "pending",
"external_id": "PIN-ARS-001",
"amount": 5000,
"currency": "ARS",
"shop_code": "your_ars_shop",
"payment_page_url": "https://api.trustedpay.one/public/payin-pages/pay_12345",
"payment_page_expires_at": "2025-12-05T10:15:00.000000Z",
"transaction_type": "payin",
"created_at": "2025-12-05T10:00:00.000000Z",
"updated_at": "2025-12-05T10:00:00.000000Z"
}

For ARS payment-page payins, empty paymentData is omitted from the create response.

The request will be validated using the standard payin fields: external_id, amount, currency and optional routing/accounting fields from the main Create payin contract.

Back to PayIn