efrilmandClaude Opus 5.5
2c9753fae7
EnakPoint can only be redeemed for vouchers now: it can no longer pay for orders and is never cashed out (docs/enakgame-prd.md §3.2, EG-001, EG-002). No order was ever paid with EnakPoint, so there is no data to move. Removed: - POST /customer/wallet/payment-code, POST /customer/orders/:id/pay-with-points and GET /orders/:id/point-payment/preview, with their processors, repositories, services, handlers and tests. - The point payment method type: paying, splitting and refunding with it, the outlet filter on the method list, and the system-method guard. - points and payment_code on CreatePayment; points_used and point_value on payments; accepts_point_payment on the customer outlets. - The outlet point_payment settings. A PUT that still sends them is rejected as an unknown field. - The EnakPoint split in the payment method analytics. - PAYMENT and PAYMENT_REFUND from the wallet type rules. Tests that used them as a generic EnakPoint debit use REWARD_REDEEM. - The EnakPoint-paid part from the earning basis, which is subtotal − discount again. Migration 000102 drops the trigger, the point methods and their index, the payments columns, and the outlet settings, and restores the method type CHECK without point. payments.payment_method_id is ON DELETE RESTRICT, so it fails rather than lose a payment made with EnakPoint. The integration docs list the removed endpoints and fields, and the EnakPoint & EnakCoin PRD and tasks note what is superseded. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
36 lines
1.5 KiB
PL/PgSQL
36 lines
1.5 KiB
PL/PgSQL
-- Brings back what 000094 and 000098 set up. The outlet settings removed by the up
|
|
-- migration are not restored: every outlet falls back to not accepting EnakPoint.
|
|
|
|
ALTER TABLE payments
|
|
ADD COLUMN IF NOT EXISTS points_used BIGINT,
|
|
ADD COLUMN IF NOT EXISTS point_value DECIMAL(10,2),
|
|
ADD CONSTRAINT chk_payments_point_pair CHECK (
|
|
(points_used IS NULL) = (point_value IS NULL)
|
|
AND (points_used IS NULL OR (points_used > 0 AND point_value > 0)));
|
|
|
|
ALTER TABLE payment_methods DROP CONSTRAINT IF EXISTS payment_methods_type_check;
|
|
ALTER TABLE payment_methods ADD CONSTRAINT payment_methods_type_check
|
|
CHECK (type IN ('cash', 'card', 'digital_wallet', 'qr', 'edc', 'delivery', 'point'));
|
|
|
|
CREATE UNIQUE INDEX uq_payment_methods_point_per_organization ON payment_methods(organization_id)
|
|
WHERE type = 'point';
|
|
|
|
INSERT INTO payment_methods (organization_id, name, type, is_active)
|
|
SELECT id, 'EnakPoint', 'point', TRUE FROM organizations
|
|
ON CONFLICT (organization_id) WHERE type = 'point' DO NOTHING;
|
|
|
|
CREATE OR REPLACE FUNCTION create_point_payment_method()
|
|
RETURNS TRIGGER AS $$
|
|
BEGIN
|
|
INSERT INTO payment_methods (organization_id, name, type, is_active)
|
|
VALUES (NEW.id, 'EnakPoint', 'point', TRUE)
|
|
ON CONFLICT (organization_id) WHERE type = 'point' DO NOTHING;
|
|
RETURN NEW;
|
|
END;
|
|
$$ LANGUAGE plpgsql;
|
|
|
|
CREATE TRIGGER trigger_create_point_payment_method
|
|
AFTER INSERT ON organizations
|
|
FOR EACH ROW
|
|
EXECUTE FUNCTION create_point_payment_method();
|