feat(loyalty): EnakPoint payment method

Adds the system payment method for paying with EnakPoint
(docs/prd-point-coin.md F9, §8, §10.5, PC-303).

Migration 000094 allows the point type, keeps one per organization with a
partial unique index, creates it for every existing organization, and adds
a trigger that creates it for new ones, as the walk-in customer is. It adds
payments.points_used and point_value. Their CHECK is written so it can
never be NULL: the PRD form, (both NULL) OR (both > 0), is NULL for
points_used with a NULL point_value, which a CHECK lets through, so a
payment could have lost the value a refund depends on. A test caught it.

The API cannot create, delete or retype the EnakPoint method, nor turn
another method into one; that answers 400. Renaming it is allowed. The
method list takes the outlet from ?outlet_id= or the user's outlet and
leaves EnakPoint out when that outlet does not accept it, filtered in the
query so the count stays right. The organization-wide active list is
unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

This commit is contained in:

efrilm

2026-09-30 11:33:25 +07:00

co-authored by

Claude Opus 5.5

parent fe2f459b03

commit cf5332c281

13 changed files with 274 additions and 24 deletions

									
										internal/validator/payment_method_validator.go
									
		+1
		
												View File
												
				@@ -95,6 +95,7 @@ func (v *PaymentMethodValidatorImpl) isValidPaymentMethodType(paymentMethodType

						string(constants.PaymentMethodTypeDigitalWallet),

						string(constants.PaymentMethodTypeQR),

						string(constants.PaymentMethodTypeEDC),

						string(constants.PaymentMethodTypePoint),

					}

					for _, validType := range validTypes {