Connect Claude & ChatGPT to Braintree

21 tools for Braintree

These tools are switched on when you connect. You can switch any of them off, or require your approval before it runs.

• add_dispute_text_evidenceChanges dataAdd text evidence to a dispute. Pass `input.disputeId`, `input.content` and optionally a `category` such as TRACKING_NUMBER or PURCHASER_EMAIL_ADDRESS.
• add_package_trackingChanges dataAdd shipping tracking to a transaction. Pass `input.transactionId`, `carrier` and `trackingNumber`; `notifyPayer` sends the buyer a notification.
• cancel_subscriptionDeletesCancel a subscription so no further charges are made. Pass `input.subscriptionId`. A cancelled subscription cannot be restarted.
• convert_legacy_idChanges dataConvert an ID shown in the Braintree Control Panel (`legacy_id`) to the API ID other tools need. Set `type`, e.g. TRANSACTION, CUSTOMER, DISPUTE or REFUND.
• create_customerChanges dataCreate a customer. Pass `input.customer` with firstName, lastName, email, company, phoneNumber, website and custom fields.
• create_subscriptionChanges dataStart a subscription for a saved payment method. Pass `input.planId` and `input.paymentMethodId`, plus optional price, start date or trial. The customer will be charged on the plan's schedule.
• delete_customerDeletesPermanently delete a customer and their saved payment methods. Pass `input.customerId`. This cannot be undone.
• get_current_userChanges dataGet the Braintree user and merchant account this connection uses (name, email, roles, company). Use to confirm which account you are working in.
• get_recordChanges dataGet any Braintree record (transaction, customer, refund, dispute, subscription) by its GraphQL `id`.
• list_plansChanges dataList the subscription plans set up in Braintree, with IDs, names, billing frequency and number of billing cycles.
• refund_transactionMoves moneyRefund a settled transaction. Pass `input.transactionId` and optionally `input.refund.amount` for a partial refund. Moves money back to the customer and cannot be undone.
• remove_dispute_evidenceDeletesRemove a piece of evidence from a dispute before it is submitted. Pass `input.disputeId` and `input.evidenceId`.
• search_customersChanges dataSearch customers. Pass `input` with filters such as email {is: ...}, firstName, lastName, company or createdAt range; page with `first`/`after`.
• search_disputesChanges dataSearch disputes (chargebacks). Pass `input` with filters such as status, type, reason, receivedDate or replyByDate; page with `first`/`after`.
• search_refundsChanges dataSearch refunds. Pass `input` with filters such as id, status, amount or createdAt range; page with `first`/`after`.
• search_subscriptionsChanges dataSearch subscriptions. Pass `input` with filters such as status, planId, price, daysPastDue or createdAt range; page with `first`/`after`.
• search_transactionsChanges dataSearch transactions. Pass `input` with filters such as id, status, amount, customer, orderId or createdAt range; page with `first`/`after`.
• submit_dispute_evidenceVisible to othersFinalize a dispute and send all added evidence to the card network for review. Pass `input.disputeId`. Evidence can no longer be changed afterwards.
• update_customerChanges dataUpdate a customer. Pass `input.customerId` and `input.customer` with the fields to change (name, email, company, phone and so on).
• update_subscriptionChanges dataChange a subscription. Pass `input.subscriptionId` and the fields to change, such as price, planId, paymentMethodId or number of billing cycles.
• void_transactionDeletesVoid (cancel) a transaction that is authorized or submitted for settlement but not yet settled. Pass `input.transactionId`. The customer is not charged; this cannot be undone.

Questions