Payments reference

This page is a field-level lookup. For task steps, see how to connect a payment gateway and how to manage payments. For the reasoning behind these fields, see payments: concepts.

Payment gateways

Gateway	Status
Stripe	Supported

Payment fields

Field	Description
Customer	Who the payment is from.
Type	Payment or tax withheld.
Payment method	How the money moved. See payment methods below.
Amount, currency	How much was collected, and in what currency.
Transaction ID	An external identifier, useful for avoiding duplicate entries on re-import.
Payment date	When the payment occurred.
Invoices	One or more invoices the payment is applied to, each with its own allocated amount.
Description	Optional free-text note.
Status	See payment status below.

Payment methods

Method	Description
Card	Credit, debit, or prepaid card.
Bank transfer	A direct transfer between bank accounts, including most regional direct-debit and credit-transfer rails, which Zenskar normalizes into this category rather than tracking each one separately.
Direct debit	A pre-authorized pull from the customer’s bank account.
Cash	Collected in cash.
Cheque	Collected by cheque.
UPI	India’s real-time, bank-credential-based payment system.
Netbanking	Online payment using bank credentials, common in India.
Other	Anything that doesn’t map to one of the categories above.

Manually added payments can only be recorded as bank transfer, cheque, cash, or card. The rest are populated automatically from gateway data.

Payment status

Status	Description
Created	The payment record exists, processing hasn’t completed.
In progress	Being processed by the gateway.
Requires action	The gateway needs more input, for example 3D Secure authentication.
Pending charge	Charge submitted, awaiting confirmation.
Authorized	Funds are authorized but not yet captured.
Success	The payment completed successfully.
Failed	The payment attempt failed.
Canceled	The payment was canceled before completing.
Voided	The payment was voided.
Refunded	The full amount was refunded.
Partially refunded	Part of the amount was refunded.

Refund destinations

Destination	Description
Original payment method	Refunded back through the gateway to however the customer paid.
Credits	Refunded into the customer’s Zenskar wallet as credit.
External	Tracked as a refund you’ve handled outside Zenskar.

How a payment affects invoice status

Invoice amount due after payment	Resulting status
Zero	Paid
Greater than zero, but reduced	Partially paid

Accounting entries

Payment type	Debit	Credit
Gateway-collected payment	Payment Gateways (accounts receivable)	Customers (accounts receivable)
Cash or cheque payment	Cash	Customers (accounts receivable)
Tax withheld	Tax receivable	Customers (accounts receivable)
Refund to original method or external	Customers (accounts receivable)	Cash
Refund to wallet credit	Customers (accounts receivable)	Customer wallet

Gateway fees, when reported by the gateway, are broken out into their own expense entries rather than netted against the payment amount.

What’s not yet available

Automatic retry of a failed charge using an alternative payment method. See default payment method: concepts.
Setting a customer’s default payment method from within Zenskar. It’s currently mirrored from Stripe.
Payment gateways other than Stripe.

Getting started

Product modules

Security

Model context protocol (MCP)

Pricing models

Third-party integrations

Zenskar versioning

Payment gateways

Payment fields

Payment methods

Payment status

Refund destinations

How a payment affects invoice status

Accounting entries

What’s not yet available

​Payment gateways

​Payment fields

​Payment methods

​Payment status

​Refund destinations

​How a payment affects invoice status

​Accounting entries

​What’s not yet available

Payment gateways

Payment fields

Payment methods

Payment status

Refund destinations

How a payment affects invoice status

Accounting entries

What’s not yet available