![levelsio's tweet photo. ✅ Done
💳 Made an auto-dispute response system for Interior AI to see how easy it'd be
It syncs old disputes but also catches new disputes via Stripe webhook and then auto submits evidence to try win them, it even includes the interior designs they generated in the evidence PDF to prove they used it!
Here's the prompt/skill I made:
----
Build an auto-dispute-response system for Stripe that:
1. Shared evidence collection (app/dispute_evidence.php)
Create a shared file with functions used by both the webhook and sync worker. This avoids duplicating evidence logic.
Key functions:
- getDisputeUserPlan($user, $stripe) — pulls the user's subscription plan from Stripe API (source of truth, since local DB plan field gets cleared on cancellation). Falls back to local DB fields if Stripe call fails. Maps product IDs to plan names and includes price/interval and canceled status.
- collectDisputeEvidence($stripe, $user, $email, $charge, $photosDb) — collects all text and file evidence, returns an array ready to submit to Stripe.
- generateServiceDocPdf($stripe, $user, $email, $photos_done, $recent_photos, $total_amount_paid) — generates a PDF with customer info, usage summary, recent activity table, and up to 6 actual product images (resized to JPEG at 500px wide / quality 75 to stay under Stripe's 5MB file upload limit). Returns both the Stripe file ID and raw PDF data.
Important: pull total_amount_paid from Stripe charges API (sum of succeeded, non-refunded charges) instead of trusting the local DB which can be null/stale.
2. Webhook handler (in stripe_webhook.php)
Catch `charge.dispute.created` events. When a dispute comes in:
- Get the dispute, charge, and customer objects from Stripe
- Look up the user in the local database by stripe_customer_id
- Save the dispute to a `disputes` SQLite database (fields: dispute_id, charge_id, payment_intent_id, stripe_customer_id, user_id, email, amount, currency, reason, status, epoch_created, epoch_evidence_submitted, evidence_json, stripe_response, epoch_resolved, outcome)
- Call collectDisputeEvidence() to collect all evidence (text + file uploads)
- Submit evidence to Stripe via $stripe->disputes->update($dispute_id, ['evidence' => $evidence])
- Send a Telegram notification that a new dispute came in and evidence was auto-submitted
Also catch `charge.dispute.updated` and `charge.dispute.closed` events to track dispute outcomes (won/lost) in the database and send Telegram notifications with the result (with emoji: checkmark for won, x for lost, warning for other).
3. Evidence fields submitted to Stripe
TEXT fields (write strings directly):
- product_description — describe what the product/service is
- customer_name — from Stripe customer object
- customer_email_address — from Stripe customer object
- access_activity_log — detailed usage log: signup date, number of items/actions done, last active date, subscription plan (from Stripe), platform, total amount paid (from Stripe), recent activity with timestamps
- uncategorized_text — the "why we should win" argument: customer signed up on X, actively used the service doing Y things, total amount paid, service was delivered digitally/instantly, customer never contacted us for a refund before disputing
- refund_policy_disclosure — when the refund policy was presented (during checkout, always accessible at /legal)
- cancellation_policy_disclosure — when cancellation policy was shown (during checkout, accessible at /legal, can cancel anytime from dashboard)
- refund_refusal_explanation — customer didn't contact us for a refund before filing the dispute
- cancellation_rebuttal — proof customer actively used the service and never requested cancellation
- service_date — date of the charge (Y-m-d format)
FILE UPLOAD fields (upload file to Stripe first via $stripe->files->create(['purpose'=>'dispute_evidence', 'file'=>fopen($path,'r')]), then pass the returned file_xxxxx ID):
- receipt — pull the invoice PDF directly from Stripe ($stripe->invoices->retrieve($charge->invoice)->invoice_pdf gives a ready-made PDF URL, just download it and upload as dispute evidence)
- service_documentation — generate a PDF containing: customer info section, service usage summary, recent activity table, and up to 6 actual product images/screenshots the customer received. Resize images before embedding (500px wide, JPEG quality 75) to stay under Stripe's 5MB file upload limit.
Also save both PDFs to your file storage (e.g. Cloudflare R2, S3) with hashed filenames so they're not guessable but viewable from the admin dashboard.
Store the storage URLs in the evidence_json as _receipt_r2_url and _service_doc_r2_url (underscore prefix so they're easy to identify as internal fields).
DO NOT use these fields for text — they expect file upload IDs only:
service_documentation, cancellation_policy, refund_policy, customer_communication, customer_signature, receipt, shipping_documentation, duplicate_charge_documentation, uncategorized_file
4. CLI sync worker (workers/syncDisputes.php)
A script that pulls ALL existing disputes from Stripe's API (paginated with $stripe->disputes->all(['limit' => 100]) and starting_after for pagination), saves them to the local disputes database, and for any that still have needs_response or warning_needs_response status and haven't had evidence submitted yet — auto-submits evidence using the shared collectDisputeEvidence() function. This is needed because the webhook only catches future disputes, not existing ones. Too heavy to run on frontend — run via CLI only (php workers/syncDisputes.php). Saves a JSON cache file with sync results so the dashboard can show last sync time.
5. Mini dashboard (disputes.php with ?key= auth)
A simple HTML page protected by ?key= query parameter that shows:
- Stats boxes: total disputes, pending, won, lost, disputed last 30 days (amount + count), disputed last 12 months (amount + count), total $ disputed
- A note showing the CLI sync command and last sync time from cache
- A test form where you enter a stripe_customer_id to preview what evidence would be submitted (without actually submitting) — useful for debugging
- A table of all disputes: date, email, amount, reason, status (color-coded badges), evidence submission status, links to both detail view and Stripe dashboard
Detail view (action=view&id=dispute_id):
- Shows all dispute info, link to Stripe, and a "Regenerate Evidence" button
- Shows PDF file links (receipt + service documentation) if available
- Shows Stripe file upload IDs
- Shows all text evidence fields
Regenerate Evidence (action=regen&id=dispute_id):
- Regenerates the receipt and service documentation PDFs and uploads to file storage
- Updates the evidence_json in the database with new PDF URLs
- IMPORTANT: Use fastcgi_finish_request() to send the HTTP response immediately (redirect back to detail page with "regenerating in background" notice), then continue generating PDFs in the background. This prevents frontend timeouts since downloading images and generating PDFs can take 30+ seconds.
Add an nginx rewrite for the page (e.g. rewrite ^/disputes/?$ /disputes.php). Make sure it's in the correct nginx config file (check which one the symlink in sites-enabled actually points to).
6. Telegram notifications
- New dispute: "{site name} - New dispute from {email} for ${amount} ({reason}). Evidence auto-submitted to Stripe. {stripe_dashboard_link}"
- Evidence failed: "{site name} - New dispute from {email} for ${amount} ({reason}). Evidence submission FAILED: {error}"
- Dispute won: "{site name} - Dispute WON (checkmark) for {email} - ${amount} ({reason}) {stripe_dashboard_link}"
- Dispute lost: "{site name} - Dispute LOST (x) for {email} - ${amount} ({reason}) {stripe_dashboard_link}"
- DB permission error: "{site name} - DISPUTE DB ERROR: {error} - check permissions on data/disputes.db"
7. Make sure these Stripe webhook events are enabled in the Stripe dashboard:
- charge.dispute.created
- charge.dispute.updated
- charge.dispute.closed
8. Database permissions
The disputes.db file must be writable by the web server user (e.g. www-data). If you create it from CLI as root, fix ownership to match your other DB files. PHP-FPM runs as a different user than root.
9. Dependencies
- FPDF (setasign/fpdf) for PDF generation — install via composer require setasign/fpdf
- GD extension for image resizing (usually already installed)
- Stripe PHP SDK (already installed if you have Stripe webhooks)
- AWS S3 SDK for R2/S3 uploads (already installed if using Cloudflare R2)](https://pbs.twimg.com/media/HFOKimFXUAAPhpy.png)
![levelsio's tweet photo. ✅ Done
💳 Made an auto-dispute response system for Interior AI to see how easy it'd be
It syncs old disputes but also catches new disputes via Stripe webhook and then auto submits evidence to try win them, it even includes the interior designs they generated in the evidence PDF to prove they used it!
Here's the prompt/skill I made:
----
Build an auto-dispute-response system for Stripe that:
1. Shared evidence collection (app/dispute_evidence.php)
Create a shared file with functions used by both the webhook and sync worker. This avoids duplicating evidence logic.
Key functions:
- getDisputeUserPlan($user, $stripe) — pulls the user's subscription plan from Stripe API (source of truth, since local DB plan field gets cleared on cancellation). Falls back to local DB fields if Stripe call fails. Maps product IDs to plan names and includes price/interval and canceled status.
- collectDisputeEvidence($stripe, $user, $email, $charge, $photosDb) — collects all text and file evidence, returns an array ready to submit to Stripe.
- generateServiceDocPdf($stripe, $user, $email, $photos_done, $recent_photos, $total_amount_paid) — generates a PDF with customer info, usage summary, recent activity table, and up to 6 actual product images (resized to JPEG at 500px wide / quality 75 to stay under Stripe's 5MB file upload limit). Returns both the Stripe file ID and raw PDF data.
Important: pull total_amount_paid from Stripe charges API (sum of succeeded, non-refunded charges) instead of trusting the local DB which can be null/stale.
2. Webhook handler (in stripe_webhook.php)
Catch `charge.dispute.created` events. When a dispute comes in:
- Get the dispute, charge, and customer objects from Stripe
- Look up the user in the local database by stripe_customer_id
- Save the dispute to a `disputes` SQLite database (fields: dispute_id, charge_id, payment_intent_id, stripe_customer_id, user_id, email, amount, currency, reason, status, epoch_created, epoch_evidence_submitted, evidence_json, stripe_response, epoch_resolved, outcome)
- Call collectDisputeEvidence() to collect all evidence (text + file uploads)
- Submit evidence to Stripe via $stripe->disputes->update($dispute_id, ['evidence' => $evidence])
- Send a Telegram notification that a new dispute came in and evidence was auto-submitted
Also catch `charge.dispute.updated` and `charge.dispute.closed` events to track dispute outcomes (won/lost) in the database and send Telegram notifications with the result (with emoji: checkmark for won, x for lost, warning for other).
3. Evidence fields submitted to Stripe
TEXT fields (write strings directly):
- product_description — describe what the product/service is
- customer_name — from Stripe customer object
- customer_email_address — from Stripe customer object
- access_activity_log — detailed usage log: signup date, number of items/actions done, last active date, subscription plan (from Stripe), platform, total amount paid (from Stripe), recent activity with timestamps
- uncategorized_text — the "why we should win" argument: customer signed up on X, actively used the service doing Y things, total amount paid, service was delivered digitally/instantly, customer never contacted us for a refund before disputing
- refund_policy_disclosure — when the refund policy was presented (during checkout, always accessible at /legal)
- cancellation_policy_disclosure — when cancellation policy was shown (during checkout, accessible at /legal, can cancel anytime from dashboard)
- refund_refusal_explanation — customer didn't contact us for a refund before filing the dispute
- cancellation_rebuttal — proof customer actively used the service and never requested cancellation
- service_date — date of the charge (Y-m-d format)
FILE UPLOAD fields (upload file to Stripe first via $stripe->files->create(['purpose'=>'dispute_evidence', 'file'=>fopen($path,'r')]), then pass the returned file_xxxxx ID):
- receipt — pull the invoice PDF directly from Stripe ($stripe->invoices->retrieve($charge->invoice)->invoice_pdf gives a ready-made PDF URL, just download it and upload as dispute evidence)
- service_documentation — generate a PDF containing: customer info section, service usage summary, recent activity table, and up to 6 actual product images/screenshots the customer received. Resize images before embedding (500px wide, JPEG quality 75) to stay under Stripe's 5MB file upload limit.
Also save both PDFs to your file storage (e.g. Cloudflare R2, S3) with hashed filenames so they're not guessable but viewable from the admin dashboard.
Store the storage URLs in the evidence_json as _receipt_r2_url and _service_doc_r2_url (underscore prefix so they're easy to identify as internal fields).
DO NOT use these fields for text — they expect file upload IDs only:
service_documentation, cancellation_policy, refund_policy, customer_communication, customer_signature, receipt, shipping_documentation, duplicate_charge_documentation, uncategorized_file
4. CLI sync worker (workers/syncDisputes.php)
A script that pulls ALL existing disputes from Stripe's API (paginated with $stripe->disputes->all(['limit' => 100]) and starting_after for pagination), saves them to the local disputes database, and for any that still have needs_response or warning_needs_response status and haven't had evidence submitted yet — auto-submits evidence using the shared collectDisputeEvidence() function. This is needed because the webhook only catches future disputes, not existing ones. Too heavy to run on frontend — run via CLI only (php workers/syncDisputes.php). Saves a JSON cache file with sync results so the dashboard can show last sync time.
5. Mini dashboard (disputes.php with ?key= auth)
A simple HTML page protected by ?key= query parameter that shows:
- Stats boxes: total disputes, pending, won, lost, disputed last 30 days (amount + count), disputed last 12 months (amount + count), total $ disputed
- A note showing the CLI sync command and last sync time from cache
- A test form where you enter a stripe_customer_id to preview what evidence would be submitted (without actually submitting) — useful for debugging
- A table of all disputes: date, email, amount, reason, status (color-coded badges), evidence submission status, links to both detail view and Stripe dashboard
Detail view (action=view&id=dispute_id):
- Shows all dispute info, link to Stripe, and a "Regenerate Evidence" button
- Shows PDF file links (receipt + service documentation) if available
- Shows Stripe file upload IDs
- Shows all text evidence fields
Regenerate Evidence (action=regen&id=dispute_id):
- Regenerates the receipt and service documentation PDFs and uploads to file storage
- Updates the evidence_json in the database with new PDF URLs
- IMPORTANT: Use fastcgi_finish_request() to send the HTTP response immediately (redirect back to detail page with "regenerating in background" notice), then continue generating PDFs in the background. This prevents frontend timeouts since downloading images and generating PDFs can take 30+ seconds.
Add an nginx rewrite for the page (e.g. rewrite ^/disputes/?$ /disputes.php). Make sure it's in the correct nginx config file (check which one the symlink in sites-enabled actually points to).
6. Telegram notifications
- New dispute: "{site name} - New dispute from {email} for ${amount} ({reason}). Evidence auto-submitted to Stripe. {stripe_dashboard_link}"
- Evidence failed: "{site name} - New dispute from {email} for ${amount} ({reason}). Evidence submission FAILED: {error}"
- Dispute won: "{site name} - Dispute WON (checkmark) for {email} - ${amount} ({reason}) {stripe_dashboard_link}"
- Dispute lost: "{site name} - Dispute LOST (x) for {email} - ${amount} ({reason}) {stripe_dashboard_link}"
- DB permission error: "{site name} - DISPUTE DB ERROR: {error} - check permissions on data/disputes.db"
7. Make sure these Stripe webhook events are enabled in the Stripe dashboard:
- charge.dispute.created
- charge.dispute.updated
- charge.dispute.closed
8. Database permissions
The disputes.db file must be writable by the web server user (e.g. www-data). If you create it from CLI as root, fix ownership to match your other DB files. PHP-FPM runs as a different user than root.
9. Dependencies
- FPDF (setasign/fpdf) for PDF generation — install via composer require setasign/fpdf
- GD extension for image resizing (usually already installed)
- Stripe PHP SDK (already installed if you have Stripe webhooks)
- AWS S3 SDK for R2/S3 uploads (already installed if using Cloudflare R2)](https://pbs.twimg.com/media/HFOFcMIXEAA_Qc5.jpg)
Olivia
Online
또찌
@0xddogee
일, 주식, 부동산, 코인 이야기 끄적거리는 사람. 기획으로 먹고 살아요.
대한민국 서울
Joined January 2016
752 Following
1.3K Followers
2.7K Posts
@lioncho7 오호 피그마 구독까지 정리하셨다는 게 인상 깊네요. 직접 기획부터 라이브 서비스까지 하시나봐요.
저도 1인 사이드 프로젝트는 그렇게 운영하는데 회사 단위는 아무래도 책임도 있고... 개발자 분들이 더 잘 아시다보니.. 회사에서는 기획에 한정되서 진행하고 있네요.
요즘 AI를 이용해 기획하면서 제일 귀찮았던 게... 프로토타입 만들어놓고 화면정의서를 화면마다 쓰는거였어요.
그래서 프로토타입 자체가 화면정의서가 되면 안 되나? 싶어 라이브러리로 만들어봤습니다.
기획 업계분들 한번 써보시고 불편한 거 있으면 편하게 피드백 주세요, 고쳐볼게요 🙂
데모: https://t.co/LKb3sYTssQ
깃허브: https://t.co/0D3W3K2LsG
난 근데 이게 과연 좋은건지 모르겟음
장에서 영양분을 흡수하지 않고 그냥 똥으로 내보낸다는 소리인데 그게 좋은가?
장의 문제가 심각하다라는 생각이 들엇는데... 뭐 개인이 행복하면 됫지만은
쯔양의 충격적인 식후혈당
검사 1시간 전 초콜릿과 오징어를 먹고 혈당 89로 먹방 시작
치킨 100조각 음료수 4통을 먹은 후 식후혈당은….
구글이 분기 적자를 기록해서 샀다기 보다는, 버핏은 예전부터 구글을 놓친것을 실수라고 주주총회에서 여러번 언급한적이 있고, 다른 하이퍼스케일러 (아마존, 마소) 보다 자체사업의 해지와 캐시플로우가 훌륭하여 이길 확률이 높아서 산다고 봅니다.
버핏이 CNBC에서 구글 얘기한 2분이 요즘 AI capex 논쟁 전체를 정리함.
"구글이랑 경쟁자들 전부 수천억 달러를 깔고 있다. 그건 진짜 돈이다. 우리 철도 개발에도 그런 돈은 안 들어갔다. 소프트웨어 시절엔 없던 게임이다."
자산 가벼울 땐 안 사더니 capex 무거워서 주주들이 싫어하는 지금 샀냐는 질문엔 — "기록을 보면 이 회사들이 월스트리트가 파는 물건의 90~95%보다 승자가 될 확률이 높다. 월스트리트 보고서 중에 기업의 실제 내부수익률을 파고드는 걸 본 적이 없다. 다음 분기 얘기만 묻는다. 우스운 일이다."
버크셔는 이 판에 310억달러를 얹었음. 어제 구글 FCF가 22년 만에 처음 마이너스가 된 바로 그 지출을, 버핏은 사야 할 이유로 읽는 중.
@BSPK_ 난 대부분 fable로 일하는데 sonnet으로 음..
@ngyu00 지원회사 200곳
최종 5곳
오퍼 1곳
화이팅입니다..
이게 근데 앤스로픽한테도 좋은건 아님. 잠재적 판매자가 전세계인이어야 tam이 커지고 그 돈으로 R&D에 재투자하지 미국만 제한해놓으면 천장이 생겨버리는데 그러면 무조건 뒤쳐지지.
The US government, citing national security authorities, has issued an export control directive to suspend all access to Fable 5 and Mythos 5 by any foreign national, whether inside or outside the United States, including foreign national Anthropic employees.
The net effect of this order is that we must abruptly disable Fable 5 and Mythos 5 for all our customers to ensure compliance.
Access to all other Claude models is not affected.
We apologize for this disruption to our customers. We believe this is a misunderstanding and are working to restore access as soon as possible.
Read our full statement: https://t.co/bwn0sximKZ
와 fable 하루 썻는데 없어졋누;;
그래도 워크플로우 개선하긴 햇는데 변화가 잇엇는지 앞으로 테스트를 계속 해봐야겟다.
As a result of a US government directive, we are suspending access to Claude Fable 5 for all users. You can continue to use all other Claude models.
Here’s what this means for you:
Across Claude products, new sessions will run on your selected default model or Opus 4.8, and existing Fable 5 sessions will end with an error.
On the Claude Platform, requests to Fable 5 will also return an error. Please update your integrations to other Claude models.
We know this is a disruption to your workflows; we appreciate your patience and support.
@mad_dogdebt 이것도 근데 반대로 말하면 뭐 이슈 터졋다? 내 아이한테 위험한 성분이 검출됫다? 바로 매출 수직낙하임. 양날의 검
@gimhyeo02389130 사실 근데 회사도 그렇게 돌아가잖아요. 직급이 올라가면 밑에 실무자에게 일을 놔주고 디렉션과 리더십이 중요한것처럼. 비슷한거 아닐까요? 임원이 실무 쥐고 잇으면 안되죠
@bumpeng27 정치인은 말 그대로 정치를 업으로 하는 사람들인데 안짤리고 롱런하려면 소비자 눈치보면서 해달라는거 해줘야죠.
그렇게 해서 리짜이밍 여기까지 왓고 나머지 깜빵 간거 아닙네까?
나라면 눈치보고 깜빵 안가고 싶을거 같은데
@bumpeng27 저도 리짜이밍 옹호하는건 아닙니다만, 원래 자본주의 사회에서 눈치보면서 사는게 맞지 않나요? 님들도 상사가 뭐 시켯는데 좀 이상하면 철학 도덕 자격 운운하면서 안할건가요? 그냥 시장이 원하면 하는거고 그게 내 인생줄 연명하는거죠. 뭐 직장인, 전문경영인과 하는거 크게 다르지 않아보이는데
@PolarisLog 이제 주인은 국민 연금이고 소액주주인데 거기서 경영권 행사해야죠 사실은
@PolarisLog 근데.. 뭐 이재용이 최대주주이기는 한데.. 어차피 다 나라한테 상속세로 뺏길건데 굳이 그렇게 할 이유가 있을까요?
이재용도 자기 자식에게는 더이상 안(못)넘길거라고도 여러번 이야기한적이 있고...
New fun thing I did to secure my VPS even further
I installed @Cloudflare Tunnel, many of you recommended me this
I already had 443 inbound firewall limited to Cloudflare's IP range, but this is even better
Cloudflare Tunnel is outbound, which means it connects from your server to Cloudflare, and keeps the connection active, then if someone opens your site, Cloudflare sends you the package via the tunnel and your server responds
Then you can block ALL inbound traffic on your firewall (in my case the Hetzner firewall in the dashboard), so now NOBODY can ever access my server, only Cloudflare and Tailscale (which is my own subnet which just my server and my laptop on it)
You can just ask AI to set it up on the server etc., very easy
✅ Done
💳 Made an auto-dispute response system for Interior AI to see how easy it'd be
It syncs old disputes but also catches new disputes via Stripe webhook and then auto submits evidence to try win them, it even includes the interior designs they generated in the evidence PDF to prove they used it!
Here's the prompt/skill I made:
----
Build an auto-dispute-response system for Stripe that:
1. Shared evidence collection (app/dispute_evidence.php)
Create a shared file with functions used by both the webhook and sync worker. This avoids duplicating evidence logic.
Key functions:
- getDisputeUserPlan($user, $stripe) — pulls the user's subscription plan from Stripe API (source of truth, since local DB plan field gets cleared on cancellation). Falls back to local DB fields if Stripe call fails. Maps product IDs to plan names and includes price/interval and canceled status.
- collectDisputeEvidence($stripe, $user, $email, $charge, $photosDb) — collects all text and file evidence, returns an array ready to submit to Stripe.
- generateServiceDocPdf($stripe, $user, $email, $photos_done, $recent_photos, $total_amount_paid) — generates a PDF with customer info, usage summary, recent activity table, and up to 6 actual product images (resized to JPEG at 500px wide / quality 75 to stay under Stripe's 5MB file upload limit). Returns both the Stripe file ID and raw PDF data.
Important: pull total_amount_paid from Stripe charges API (sum of succeeded, non-refunded charges) instead of trusting the local DB which can be null/stale.
2. Webhook handler (in stripe_webhook.php)
Catch `charge.dispute.created` events. When a dispute comes in:
- Get the dispute, charge, and customer objects from Stripe
- Look up the user in the local database by stripe_customer_id
- Save the dispute to a `disputes` SQLite database (fields: dispute_id, charge_id, payment_intent_id, stripe_customer_id, user_id, email, amount, currency, reason, status, epoch_created, epoch_evidence_submitted, evidence_json, stripe_response, epoch_resolved, outcome)
- Call collectDisputeEvidence() to collect all evidence (text + file uploads)
- Submit evidence to Stripe via $stripe->disputes->update($dispute_id, ['evidence' => $evidence])
- Send a Telegram notification that a new dispute came in and evidence was auto-submitted
Also catch `charge.dispute.updated` and `charge.dispute.closed` events to track dispute outcomes (won/lost) in the database and send Telegram notifications with the result (with emoji: checkmark for won, x for lost, warning for other).
3. Evidence fields submitted to Stripe
TEXT fields (write strings directly):
- product_description — describe what the product/service is
- customer_name — from Stripe customer object
- customer_email_address — from Stripe customer object
- access_activity_log — detailed usage log: signup date, number of items/actions done, last active date, subscription plan (from Stripe), platform, total amount paid (from Stripe), recent activity with timestamps
- uncategorized_text — the "why we should win" argument: customer signed up on X, actively used the service doing Y things, total amount paid, service was delivered digitally/instantly, customer never contacted us for a refund before disputing
- refund_policy_disclosure — when the refund policy was presented (during checkout, always accessible at /legal)
- cancellation_policy_disclosure — when cancellation policy was shown (during checkout, accessible at /legal, can cancel anytime from dashboard)
- refund_refusal_explanation — customer didn't contact us for a refund before filing the dispute
- cancellation_rebuttal — proof customer actively used the service and never requested cancellation
- service_date — date of the charge (Y-m-d format)
FILE UPLOAD fields (upload file to Stripe first via $stripe->files->create(['purpose'=>'dispute_evidence', 'file'=>fopen($path,'r')]), then pass the returned file_xxxxx ID):
- receipt — pull the invoice PDF directly from Stripe ($stripe->invoices->retrieve($charge->invoice)->invoice_pdf gives a ready-made PDF URL, just download it and upload as dispute evidence)
- service_documentation — generate a PDF containing: customer info section, service usage summary, recent activity table, and up to 6 actual product images/screenshots the customer received. Resize images before embedding (500px wide, JPEG quality 75) to stay under Stripe's 5MB file upload limit.
Also save both PDFs to your file storage (e.g. Cloudflare R2, S3) with hashed filenames so they're not guessable but viewable from the admin dashboard.
Store the storage URLs in the evidence_json as _receipt_r2_url and _service_doc_r2_url (underscore prefix so they're easy to identify as internal fields).
DO NOT use these fields for text — they expect file upload IDs only:
service_documentation, cancellation_policy, refund_policy, customer_communication, customer_signature, receipt, shipping_documentation, duplicate_charge_documentation, uncategorized_file
4. CLI sync worker (workers/syncDisputes.php)
A script that pulls ALL existing disputes from Stripe's API (paginated with $stripe->disputes->all(['limit' => 100]) and starting_after for pagination), saves them to the local disputes database, and for any that still have needs_response or warning_needs_response status and haven't had evidence submitted yet — auto-submits evidence using the shared collectDisputeEvidence() function. This is needed because the webhook only catches future disputes, not existing ones. Too heavy to run on frontend — run via CLI only (php workers/syncDisputes.php). Saves a JSON cache file with sync results so the dashboard can show last sync time.
5. Mini dashboard (disputes.php with ?key= auth)
A simple HTML page protected by ?key= query parameter that shows:
- Stats boxes: total disputes, pending, won, lost, disputed last 30 days (amount + count), disputed last 12 months (amount + count), total $ disputed
- A note showing the CLI sync command and last sync time from cache
- A test form where you enter a stripe_customer_id to preview what evidence would be submitted (without actually submitting) — useful for debugging
- A table of all disputes: date, email, amount, reason, status (color-coded badges), evidence submission status, links to both detail view and Stripe dashboard
Detail view (action=view&id=dispute_id):
- Shows all dispute info, link to Stripe, and a "Regenerate Evidence" button
- Shows PDF file links (receipt + service documentation) if available
- Shows Stripe file upload IDs
- Shows all text evidence fields
Regenerate Evidence (action=regen&id=dispute_id):
- Regenerates the receipt and service documentation PDFs and uploads to file storage
- Updates the evidence_json in the database with new PDF URLs
- IMPORTANT: Use fastcgi_finish_request() to send the HTTP response immediately (redirect back to detail page with "regenerating in background" notice), then continue generating PDFs in the background. This prevents frontend timeouts since downloading images and generating PDFs can take 30+ seconds.
Add an nginx rewrite for the page (e.g. rewrite ^/disputes/?$ /disputes.php). Make sure it's in the correct nginx config file (check which one the symlink in sites-enabled actually points to).
6. Telegram notifications
- New dispute: "{site name} - New dispute from {email} for ${amount} ({reason}). Evidence auto-submitted to Stripe. {stripe_dashboard_link}"
- Evidence failed: "{site name} - New dispute from {email} for ${amount} ({reason}). Evidence submission FAILED: {error}"
- Dispute won: "{site name} - Dispute WON (checkmark) for {email} - ${amount} ({reason}) {stripe_dashboard_link}"
- Dispute lost: "{site name} - Dispute LOST (x) for {email} - ${amount} ({reason}) {stripe_dashboard_link}"
- DB permission error: "{site name} - DISPUTE DB ERROR: {error} - check permissions on data/disputes.db"
7. Make sure these Stripe webhook events are enabled in the Stripe dashboard:
- charge.dispute.created
- charge.dispute.updated
- charge.dispute.closed
8. Database permissions
The disputes.db file must be writable by the web server user (e.g. www-data). If you create it from CLI as root, fix ownership to match your other DB files. PHP-FPM runs as a different user than root.
9. Dependencies
- FPDF (setasign/fpdf) for PDF generation — install via composer require setasign/fpdf
- GD extension for image resizing (usually already installed)
- Stripe PHP SDK (already installed if you have Stripe webhooks)
- AWS S3 SDK for R2/S3 uploads (already installed if using Cloudflare R2)
![levelsio's tweet photo. ✅ Done
💳 Made an auto-dispute response system for Interior AI to see how easy it'd be
It syncs old disputes but also catches new disputes via Stripe webhook and then auto submits evidence to try win them, it even includes the interior designs they generated in the evidence PDF to prove they used it!
Here's the prompt/skill I made:
----
Build an auto-dispute-response system for Stripe that:
1. Shared evidence collection (app/dispute_evidence.php)
Create a shared file with functions used by both the webhook and sync worker. This avoids duplicating evidence logic.
Key functions:
- getDisputeUserPlan($user, $stripe) — pulls the user's subscription plan from Stripe API (source of truth, since local DB plan field gets cleared on cancellation). Falls back to local DB fields if Stripe call fails. Maps product IDs to plan names and includes price/interval and canceled status.
- collectDisputeEvidence($stripe, $user, $email, $charge, $photosDb) — collects all text and file evidence, returns an array ready to submit to Stripe.
- generateServiceDocPdf($stripe, $user, $email, $photos_done, $recent_photos, $total_amount_paid) — generates a PDF with customer info, usage summary, recent activity table, and up to 6 actual product images (resized to JPEG at 500px wide / quality 75 to stay under Stripe's 5MB file upload limit). Returns both the Stripe file ID and raw PDF data.
Important: pull total_amount_paid from Stripe charges API (sum of succeeded, non-refunded charges) instead of trusting the local DB which can be null/stale.
2. Webhook handler (in stripe_webhook.php)
Catch `charge.dispute.created` events. When a dispute comes in:
- Get the dispute, charge, and customer objects from Stripe
- Look up the user in the local database by stripe_customer_id
- Save the dispute to a `disputes` SQLite database (fields: dispute_id, charge_id, payment_intent_id, stripe_customer_id, user_id, email, amount, currency, reason, status, epoch_created, epoch_evidence_submitted, evidence_json, stripe_response, epoch_resolved, outcome)
- Call collectDisputeEvidence() to collect all evidence (text + file uploads)
- Submit evidence to Stripe via $stripe->disputes->update($dispute_id, ['evidence' => $evidence])
- Send a Telegram notification that a new dispute came in and evidence was auto-submitted
Also catch `charge.dispute.updated` and `charge.dispute.closed` events to track dispute outcomes (won/lost) in the database and send Telegram notifications with the result (with emoji: checkmark for won, x for lost, warning for other).
3. Evidence fields submitted to Stripe
TEXT fields (write strings directly):
- product_description — describe what the product/service is
- customer_name — from Stripe customer object
- customer_email_address — from Stripe customer object
- access_activity_log — detailed usage log: signup date, number of items/actions done, last active date, subscription plan (from Stripe), platform, total amount paid (from Stripe), recent activity with timestamps
- uncategorized_text — the "why we should win" argument: customer signed up on X, actively used the service doing Y things, total amount paid, service was delivered digitally/instantly, customer never contacted us for a refund before disputing
- refund_policy_disclosure — when the refund policy was presented (during checkout, always accessible at /legal)
- cancellation_policy_disclosure — when cancellation policy was shown (during checkout, accessible at /legal, can cancel anytime from dashboard)
- refund_refusal_explanation — customer didn't contact us for a refund before filing the dispute
- cancellation_rebuttal — proof customer actively used the service and never requested cancellation
- service_date — date of the charge (Y-m-d format)
FILE UPLOAD fields (upload file to Stripe first via $stripe->files->create(['purpose'=>'dispute_evidence', 'file'=>fopen($path,'r')]), then pass the returned file_xxxxx ID):
- receipt — pull the invoice PDF directly from Stripe ($stripe->invoices->retrieve($charge->invoice)->invoice_pdf gives a ready-made PDF URL, just download it and upload as dispute evidence)
- service_documentation — generate a PDF containing: customer info section, service usage summary, recent activity table, and up to 6 actual product images/screenshots the customer received. Resize images before embedding (500px wide, JPEG quality 75) to stay under Stripe's 5MB file upload limit.
Also save both PDFs to your file storage (e.g. Cloudflare R2, S3) with hashed filenames so they're not guessable but viewable from the admin dashboard.
Store the storage URLs in the evidence_json as _receipt_r2_url and _service_doc_r2_url (underscore prefix so they're easy to identify as internal fields).
DO NOT use these fields for text — they expect file upload IDs only:
service_documentation, cancellation_policy, refund_policy, customer_communication, customer_signature, receipt, shipping_documentation, duplicate_charge_documentation, uncategorized_file
4. CLI sync worker (workers/syncDisputes.php)
A script that pulls ALL existing disputes from Stripe's API (paginated with $stripe->disputes->all(['limit' => 100]) and starting_after for pagination), saves them to the local disputes database, and for any that still have needs_response or warning_needs_response status and haven't had evidence submitted yet — auto-submits evidence using the shared collectDisputeEvidence() function. This is needed because the webhook only catches future disputes, not existing ones. Too heavy to run on frontend — run via CLI only (php workers/syncDisputes.php). Saves a JSON cache file with sync results so the dashboard can show last sync time.
5. Mini dashboard (disputes.php with ?key= auth)
A simple HTML page protected by ?key= query parameter that shows:
- Stats boxes: total disputes, pending, won, lost, disputed last 30 days (amount + count), disputed last 12 months (amount + count), total $ disputed
- A note showing the CLI sync command and last sync time from cache
- A test form where you enter a stripe_customer_id to preview what evidence would be submitted (without actually submitting) — useful for debugging
- A table of all disputes: date, email, amount, reason, status (color-coded badges), evidence submission status, links to both detail view and Stripe dashboard
Detail view (action=view&id=dispute_id):
- Shows all dispute info, link to Stripe, and a "Regenerate Evidence" button
- Shows PDF file links (receipt + service documentation) if available
- Shows Stripe file upload IDs
- Shows all text evidence fields
Regenerate Evidence (action=regen&id=dispute_id):
- Regenerates the receipt and service documentation PDFs and uploads to file storage
- Updates the evidence_json in the database with new PDF URLs
- IMPORTANT: Use fastcgi_finish_request() to send the HTTP response immediately (redirect back to detail page with "regenerating in background" notice), then continue generating PDFs in the background. This prevents frontend timeouts since downloading images and generating PDFs can take 30+ seconds.
Add an nginx rewrite for the page (e.g. rewrite ^/disputes/?$ /disputes.php). Make sure it's in the correct nginx config file (check which one the symlink in sites-enabled actually points to).
6. Telegram notifications
- New dispute: "{site name} - New dispute from {email} for ${amount} ({reason}). Evidence auto-submitted to Stripe. {stripe_dashboard_link}"
- Evidence failed: "{site name} - New dispute from {email} for ${amount} ({reason}). Evidence submission FAILED: {error}"
- Dispute won: "{site name} - Dispute WON (checkmark) for {email} - ${amount} ({reason}) {stripe_dashboard_link}"
- Dispute lost: "{site name} - Dispute LOST (x) for {email} - ${amount} ({reason}) {stripe_dashboard_link}"
- DB permission error: "{site name} - DISPUTE DB ERROR: {error} - check permissions on data/disputes.db"
7. Make sure these Stripe webhook events are enabled in the Stripe dashboard:
- charge.dispute.created
- charge.dispute.updated
- charge.dispute.closed
8. Database permissions
The disputes.db file must be writable by the web server user (e.g. www-data). If you create it from CLI as root, fix ownership to match your other DB files. PHP-FPM runs as a different user than root.
9. Dependencies
- FPDF (setasign/fpdf) for PDF generation — install via composer require setasign/fpdf
- GD extension for image resizing (usually already installed)
- Stripe PHP SDK (already installed if you have Stripe webhooks)
- AWS S3 SDK for R2/S3 uploads (already installed if using Cloudflare R2)](https://pbs.twimg.com/media/HFOKimdasAAwnrG.jpg)
이걸로 현재 상황에서 은퇴가능한지 체크해보면 좋음
https://t.co/8ii3S0tJqS
네이버 '전업투자' 검색량 더 상승함..
@dori_coin 여러방면에서 공감하는데 아마 어느정도 대중화가 되고나면 그거에 맞춰서 또 사람들이 일할꺼라고 봅니다. 각자 밑에 수십개의 에이전트를 거느리면서 일하는 구조? 다만 지금은 격변기라 구조조정이 심할듯
꼬빌은 사는 그 당시에는 남는게 없는데 몇년 지나면 임대료가 계속 올라서 미래에 남는답니다. (그게 아니면 살 이유 없음)
제가 2019년에 매입햇는데 지금은 그때보다 월세가 80% 정도 올랏죠. (수익률도)
매매가도 미래의 인플레이션을 한 몇년 땡겨와서 받아요. (서울 중심지일수록)
ㄹㅇ... 2~300억 넘어가는 꽉 찬 메디컬, 또는 본인 사업체 실사용 아닌 이상
꼬빌 투자는 지옥 그 잡채다...
꼬빌 투자할 정도의 현금흐름, 에쿼티 가진 사람들 상황이 대부분 비슷할 텐데
걍 인생을 여기다 걸어야 함...ㅋㅋㅋ
코로나 이전에 산 사람들조차 워낙 싸게 사서 가격 많이 오르긴 했지만
그때 산 사람도 지금 시장에서 버티기가 쉽지 않음...
Last Seen Users on Sotwe
Janda Bolong
Seen from Germany
Türk İfşa 2025
Seen from Netherlands
Brando_😎🤙🏽
Seen from United States
máy bơm tinh của tini
Seen from Vietnam
İFŞA MERKEZİ VİP
Seen from United Kingdom
Đàn ông kín đáo.
Seen from Vietnam
mature granny
Seen from United Kingdom
Pretty
Seen from Austria
Sig_Radio🇮🇹📻🤠
Seen from United Kingdom
khjdvnng
Seen from India
Most Popular Users
Elon Musk 
@elonmusk
241.5M followers
Barack Obama
@barackobama
119.1M followers
Cristiano Ronaldo
@cristiano
113.7M followers
Donald J. Trump
@realdonaldtrump
111.8M followers
Narendra Modi
@narendramodi
107.2M followers
Rihanna
@rihanna
98.5M followers
NASA
@nasa
92.4M followers
Justin Bieber
@justinbieber
91.7M followers
KATY PERRY
@katyperry
89.6M followers
Taylor Swift
@taylorswift13
83.5M followers
Lady Gaga
@ladygaga
75M followers
Virat Kohli
@imvkohli
72.7M followers
Kim Kardashian
@kimkardashian
70.7M followers
YouTube
@youtube
68.8M followers
Neymar Jr
@neymarjr
65.7M followers
Bill Gates
@billgates
64.9M followers
Selena Gomez
@selenagomez
62.6M followers
The Ellen Show
@theellenshow
62.3M followers
CNN
@cnn
61.8M followers
X
@x
60.8M followers