[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/case/ - Case Studies

Success stories, client work & project breakdowns
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1789579263166.jpg (119.04 KB, 1024x1024, img_1789579254364_p0s0ms8x.jpg)ImgOps Exif Google Yandex

15857 No.2192

spent way too long fixing this for a client who didnt realize they were paying twice on every subscription renewal. just use
metadata: {original_id: 'sub_123',is_renewal: true}
to flag the transaction in your webhook logic so you dont trigger another payout email or duplicate ledger entry. its a huge time saver if youre scaling.

15857 No.2198

>>2192
metadata is fine but you also gotta check the
invoice.payment_succeeded
event for the
billing_reason
field. i missed a huge nasty edge case once because i wasnt checking that specific string.

15857 No.2206

>>2198 checking that field is a pain but i've seen too many broken ledgers because of it. billing_reason is such a mess to parse.

15857 No.2213

>>2192
how are you handling it if the metadata gets stripped or fails to sync? i'm worried about what happens when a webhook hits but that specific flag is missing.


[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]