Recharge

overview this guide outlines the steps for integrating your recharge account with recover the integration leverages the following information from recharge failed payments feed a webhook providing real time updates on all failed transactions subscription status access to up to date information on the state of recharge subscriptions customers and active payment methods retrieval of limited customer entities and active payment methods currently associated with a subscription these integrations ensure seamless functionality and reliable payment recovery configuration options recover has a few configuration options that the merchant can select from, these include dunning length required by recover, this is the length of time determined by the business in which a failed payment will be attempted to be recovered a common length many merchants settle on is 30 days end of dunning actions if configured, recover will cancel subscriptions on the merchant's behalf when an invoice is unable to be recovered by the close of the dunning cycle supported integration butter offers direct support for integrating your system with recover by assigning a dedicated butter solutions engineer this engineer will serve as your hands on resource, guiding you through the configuration process and ensuring a smooth integration with recover integration steps create recharge api key this is the first step in granting butter payments access to your recharge environment recover will use this key to integrate with your recharge account via api to manage retry attempts on your behalf it is important that the dedicated recharge api key is configured with the appropriate user role permissions to create the api key navigate to apps > api tokens > create an admin api token for the token nickname, you can use butter payments , and you can add integrations\@butterpayments com as the contact email api key permissions field permission orders read and write discounts read subscriptions read payments read and write payment methods read customers read products read if butter is taking over subscription cancellations, we would also need write access to subscriptions butter initializes recover for your account this is an automated step initiated by the butter once we receive a stripe api key from your account with all the necessary permissions after the api key has been generated and shared with butter, the butter team will initialize your account setup this automated process will include register your api key in recover provision a webhook endpoint to receive events from your recharge account provision webhooks on your account to send events to recover the webhook endpoint url will have the following syntax, though this is only visable by interacting with the recharge api webhooks recover serverless services butterpayments com/recharge/ts xxxxx where ts xxxxx is the transaction source (uniquely generated) for the webhook pre launch data ingest recover requires your recharge account to begin forwarding payment data to recover before going live during this pre launch period, no failed payments will be retried required pre launch data ingest required pre launch data ingest 7 days the purpose of this data ingestion phase is to ensure that all failed payments are fully captured by recover before it takes over managing payment retries this phase starts only after all prior setup steps have been successfully completed go live launch day with recover on launch day, your butter solutions engineer will work closely with your team to make sure all configurations are setup correctly and done in the required order disable existing recharge retry strategy the launch process requires careful sequencing to prevent duplicate retries from being executed by multiple retry systems this involves disabling recharge retries and any third party decline salvage services once this step is complete, butter will update recover to take full responsibility for managing all retry attempts on failed invoices moving forward rate limiting butter will reach out to recharge on the merchant's behalf if, based on the merchant's volume, a higher rate limit is needed post launch monitoring once you are live with recover, the butter team will be closely tracking performance of failed payments as they are ingested and then optimally scheduled for retry butterboard as part of your go live onto recover, you will receive email invitation to your butter account and access to your company's butterboard the butterboard provides realtime performance of revenue recovered, your recovery rate, and feed of most recent recovered transactions interested in working with butter to bring more revenue back to your business? reach out to us here contact\@butterpayments com