Course Platform Chargebacks: Who Responds on Teachable, Thinkific and Kajabi?

To find who handles course platform chargebacks, check the payment setup used for the disputed sale. The platform's name alone does not tell you where to respond or who owns the case. Locate the actual charge and account before you gather and submit proof.

Find the Case Route and Record Owners

Use this guide to assign the case and record owners. The online course chargeback pillar covers course promises, access and delivery. Here, find the right screen and the people who can supply each fact.

Identify the Payment Configuration for the Actual Sale

Start with the notice and charge. Note the platform, payment product, account, charge ID, amount, currency and sale date. Your school may have changed payment products. Today's default may not explain an older sale.

Check whether the sale used the platform's payment product, a connected provider or another route. Find the case and its current instructions. A course admin and payment-account owner may have different access.

Link the course and student to the charge. A learner account may hold free previews, granted access and several paid courses. Use records for the exact product and payment in dispute.

Compare Course Platform Chargeback Responsibilities

Official guidance checked November 3, 2026. Use this map within each named payment product. Region, account access and older setups can affect the route.

Sources: Teachable refunds and disputes, Thinkific Payments chargebacks, and Kajabi Payments responses.

This table helps you route the case. It does not decide who holds contractual liability. Check the agreement and account records for that question. Chargeflow's merchant-of-record guide explains the broader role.

Teachable: Separate the Current Payment Product From Other Routes

Teachable's September 9, 2026 guidance covers its new Teachable Payments setup. It separates Custom Payment Gateway handling. Find the charge under the setup used for that sale.

Supply relevant course and student records even if you submit through an embedded payment screen. Keep the offer version, access, service, cancellation and remedy facts. The screen may not hold records from a separate meeting or support tool.

Use the action and due date in the live case. Do not copy one platform's fee or clock to every course sale. For a separate account, confirm who receives the reply and which admin can submit it.

Thinkific: Join Student Evidence to the Payment Case

Thinkific's Payments guide lists course, activity, policy and message records. Choose those that answer the claim. A completion flag does not prove that you supplied every live session or feedback item.

Match platform records to what the student bought. For a missing lesson, check the course version, release dates, access rights and faults. For missing feedback, find proof that you sent it. LMS progress alone cannot show that work.

Check the current notice for the route and due date. Do not assume that a course platform decides the case or holds all proof. You may need records from outside teaching tools.

Kajabi: Locate the Dispute and the Specific Transaction

Kajabi's response instructions point to Payments → Disputes. Its transaction-details guide separates purchase, plan and subscription views. Find the specific charge. An offer's status is not the case status.

Save the offer, included products, relevant progress, messages and paid credits. An offer may bundle several products or future payments. Identify the service and collected charge in dispute.

Kajabi relays case details; the issuing bank decides the dispute in that payment setup. Clear records do not guarantee a win. If you find missing service or an owed remedy, address the gap before deciding to contest.

Use an Evidence-Export Ownership Checklist

Assign a source owner to each fact the claim needs. Payment and LMS screens may not tell the full story. The checklist below helps you find records. It does not promise that every plan has the same export tool.

Keep source dates, IDs and field meanings with exports. A “completed” column may reflect a student click or staff flag. Check what it means. Save the original file and mark your added notes clearly.

Worked Case: One Platform, Two Payment Routes

Hypothetical example: A school sells one $300 course through a current platform payment product and an older connected account. Case C-1 concerns the older sale. An admin sees the student in today's LMS but cannot find the case in the current dispute list.

Check the original charge and account. Do not create a duplicate reply in today's screen. Use the LMS for course records and the actual payment account for the case route. Keep both linked to the sale.

If you cannot find the charge, leave that gap open. A matching name or amount is not enough. Ask the account owner for the missing reference before you attach another payment's records.

Distinguish Inquiries, Formal Cases and Refund Requests

A support request, provider inquiry and formal chargeback can need different actions. Use the stage in the notice. A reply to one event may not satisfy a later case with its own deadline.

Keep access changes, future payment cancellation and refunds separate. Check provider rules and your duties before restricting access. Record the time and reason. A later restriction must not hide an earlier access fault.

Use the course installment guide for fixed plans. Use the offer-versus-delivery article for a delivery claim. Coaching may also need the session ledger.

Review the Packet Before Final Submission

Check the case ID, claim, due date, records and actual remedy status. Verify file rules and the final-submit step. Save the confirmation and exact proof sent. A task marked “done” in your tracker is not enough.

Keep claims within the proof. Course use does not prove payer consent. A completed course may still lack promised feedback. Refund approval does not show that money returned.

After the decision, match the result to real payment movements. Keep fees, refunds and principal apart. An offer status and case result describe different things. Do not combine them into one unexplained metric.

Verify Automation Against the Actual Configuration

Map the platform, payment account and outside records before you assess automation. Check which account can connect, which proof is available and which needs an owner. This guide does not establish a native Chargeflow connection to Teachable, Thinkific or Kajabi.

Use Chargeflow Automation to assess supported evidence and response workflows. Bring your actual setup and an anonymized case. Confirm connections and record access with the team.

Sources checked: November 3, 2026. Worksheets are editorial tools. Case IDs, amounts and timelines are hypothetical. They do not show customer results or forecast recovery. Check current provider and case rules before you submit.