Providers
Paycell PAYE

Paycell PAYE

Paycell PAYE uses provider code PAYCELL_PAYE within Lunixi Meal Cards. It is separate from Paycell card POS, wallet and mobile billing connections. Customers select an eligible PAYE card; this flow does not use QR, 2D/3D, installments or preauthorization.

Connection and environment

Create the Paycell PAYE connection in the panel using provider-issued credentials. The TEST/LIVE environment must match your connection and the permissions issued for your account. A catalog entry alone does not enable payments for your account.

TRY and a single charge are supported. Use the shared API and Checkout Form contract. Prepare the PAYE requirements below for both entry paths.

Order and customer data

Your merchant server must establish the customer's login/phone binding before creating the payment or form. Initial order metadata requires two separate objects:

FieldContent
paycellPaye.mealPer1AmountRequired digit string produced by your merchant tax system under the Paycell contract
paycellPaye.mealPer1TaxRequired digit string produced by your merchant tax system under the Paycell contract
paycellPayeAuthorization.customerIdVerified customer identifier in your merchant system
paycellPayeAuthorization.msisdnPhone number including country code, e.g. 905321234567
paycellPayeAuthorization.orderIdThe same order identifier as the payment's orderId
paycellPayeAuthorization.verificationReferenceAudit reference for the login/phone verification; never a password, OTP or access token

paycellPayeAuthorization is your merchant server's customer-context attestation, not a Paycell token. The merchant is responsible for the truth of the customer/phone verification and any provider-required permissions. Entering another phone number and checking a box does not establish that context.

The tax fields are not buyer inputs. Obtain their units and calculation rules from your provider contract; do not infer a rate or conversion from amount. The payment's main amount is always integer kurus.

Initial mealCard fields follow the methods response's inputFields: gsmNumber and the customer's dataSharingConsent. Use provider code PAYCELL_PAYE. Do not preselect sharing consent on the buyer's behalf.

Card selection and result

The start response returns an INPUT action. Its action.input.fields includes the payeCard selection field with masked labels and choices for eligible cards in that payment. Send the customer's selected value through the existing action confirm contract:

{
  "fields": {
    "payeCard": "<choice supplied by the action>"
  }
}

Do not manufacture a card number or provider card identifier; use only the returned choice. Selecting a card does not confirm a charge. Track the definitive result through the payment record and webhooks.

Cancellation, refunds and reconciliation

PAYE supports full cancellation on the charge's reconciliation day and full refunds on later reconciliation days. Partial refunds are not supported. Use panel/API operations according to the connection's supported permissions; Metropol's partial-refund or same-batch rules do not apply to PAYE.

API reconciliation uses the provider's daily transaction statement. Uncertain charge or reversal results must not trigger another financial request; follow the existing payment and operation records. The statement alone does not prove that a net bank payout has arrived.