Payment Acceptance Status

This endpoint tells you whether your account can accept new payments right now. If payment acceptance is paused, the response also lists the reasons.

While payment acceptance is paused, POST /v1/payments and POST /v1/payment-links are rejected with 403 payment_acceptance_held. Completing payments you created earlier, querying payments, and refunds are not affected.

Enabling the check

Paytalya enables this check for all accounts. Until it is enabled, holds is returned empty and payment_acceptance_held is not produced.

Request

GET /v1/payment-acceptance
Authorization: Bearer ldg_live_…

There is no request body and no parameter. The response always describes the account that owns the API key.

Response

200 OK:

{
  "acceptingPayments": false,
  "partnerStatus": "active",
  "holds": [
    {
      "reason": "agreements_pending",
      "effective": true,
      "effectiveAt": "2026-11-01T21:00:00Z",
      "since": "2026-10-02T09:15:00Z",
      "agreements": [
        {
          "agreementCode": "uye-isyeri-sozlesmesi",
          "agreementName": "Üye İşyeri Hizmet Sözleşmesi",
          "version": "2",
          "requirement": "consent",
          "kind": "first",
          "deadlineAt": "2026-11-01T21:00:00Z",
          "lastDay": "2026-11-01",
          "expired": true,
          "effectiveAt": "2026-11-01T21:00:00Z"
        }
      ]
    }
  ]
}

Field	Description
acceptingPayments	Whether your account can accept new payments right now. Always false when the account status is suspended or closed.
partnerStatus	Account status: active, suspended, or closed.
holds	Active reasons that pause payment acceptance. An empty list is returned while the check is not enabled. Sorted by effectiveAt ascending.
holds[].reason	agreements_pending or admin_hold (see below).
holds[].effective	Whether the reason is in effect now. If false, the reason starts at effectiveAt. Whether you can accept payments is always given by acceptingPayments; if another reason is in effect, payment acceptance stays paused.
holds[].effectiveAt	When the reason started or will start (UTC, ISO-8601).
holds[].since	When the reason was recorded (UTC, ISO-8601).
holds[].agreements	Filled only for agreements_pending; lists the agreements you have not completed. null for other reasons.
agreements[].requirement	consent (approval in the panel) or wet_signature (wet signature).
agreements[].kind	first (first approval) or renewal.
agreements[].deadlineAt	When the window expires (UTC). null when there is no window.
agreements[].lastDay	The last day you can complete the agreement (Türkiye time, inclusive). null when there is no window.
agreements[].expired	Whether the window has expired.

Reasons

agreements_pending

Your account has an agreement to approve, or to deliver with a wet signature, and its window has expired. Approve the agreement on the agreements screen of the Lydia Gate panel. For an agreement that needs a wet signature, send the signed document to Paytalya. Once the agreement is completed, this reason is removed automatically. If no other reason is in effect, payment acceptance resumes.

admin_hold

Paytalya paused payment acceptance. New accounts also carry this reason until account setup is completed and approved. Contact the Paytalya support team for details.

Recommendations

• You do not need to call this endpoint before every payment or payment link. Call it when you receive 403 payment_acceptance_held, to learn the reason.
• Sending the same request again does not change the result. Resolve the reason first.
• While payment acceptance is paused, buyers who open an existing payment link see an information page instead of the card form. Detail: Payment links.

Possible errors

Code	HTTP	Reason
rate_limited	429	The source-IP rate limit was exceeded. Retry after the Retry-After duration.

An authentication failure returns 401. Full list: Error Codes.