Justt.AI
Connect Recurly to Justt's AI-powered chargeback dispute platform to automatically apply subscription and invoice actions based on dispute outcomes.
Definition
Prerequisites
- You must have an active Justt.ai account.
- Your Recurly site must be using one of the supported payment gateways: Stripe, Braintree, PayPal Complete, or Adyen.
- You must have the Justt.ai and Chargeback Management feature flags enabled on your Recurly site. Contact Recurly Support to request access.
- You must have a Recurly API key available to share with Justt during setup.
Limitations
- Merchants can only use one chargeback management system at a time — either Recurly's native chargeback handling or Justt. Once Justt is enabled, Recurly stops processing gateway chargeback events for supported gateways.
- Only credit card chargebacks are processed. Non-credit card disputes — such as ACH — are not actioned.
- Each merchant site can have one active Justt configuration.
Key benefits
Key details
How the integration works
The Justt.ai integration follows a five-step setup flow:
Configure your chargeback actions
In the Recurly UI, navigate to Configuration > Invoice Templates > Invoice Settings and choose what Recurly should do when it receives a chargeback event.
Supported gateways
The Justt integration processes chargebacks from the following payment service providers (PSPs):
Chargeback actions
Recurly can be configured to take the following actions when a chargeback dispute is resolved as lost (meaning the subscriber wins the dispute):
| Action | What Recurly does |
| Create a refund | Recurly issues a refund invoice against the original transaction. |
| Expire the subscription | Recurly immediately expires the associated subscription. |
| Manually process chargebacks | Recurly sends a webhook notification only — no automatic action is taken. |
lost — such as pending, won, or under_review — are recorded in the chargeback index for visibility but do not trigger subscription actions.Webhook events
Recurly listens for two webhook event types from Justt:
| Event | When it fires |
chargeback.created | A new chargeback dispute is opened. |
chargeback.updated | The status of an existing dispute changes. |
Each event is processed independently and creates a new record in the Justt chargeback index table.
Chargeback index page
Once the integration is active, a chargeback index table appears on the Justt integration page under Integrations > Justt.ai. The table displays:
- Account (subscriber display name)
- Invoice number
- Chargeback ID
- Status
- Created date
Refund transactions
When Recurly creates a refund as a result of a Justt chargeback, the refund transaction displays "Processed by Justt" in the transaction summary. The transaction detail page also shows the reason code, chargeback reason message, and merchant reference from the original Justt webhook payload.
Disabling and re-enabling the integration
You can disable the Justt integration at any time from the Justt integration page in Recurly. Disabling it stops Recurly from processing new Justt webhooks. To remove the integration entirely, contact Recurly Support to turn off the feature flag.
FAQs
Can I use Recurly's native chargeback handling and Justt at the same time?
No. Recurly supports only one chargeback management system per site at a time. When the Justt integration is active, Recurly stops processing gateway-level chargeback events and relies solely on Justt webhooks instead.
What happens to my existing chargebacks if I disable the integration?
Disabling the integration stops the processing of new webhooks from Justt. Existing chargeback records in Recurly are not deleted and remain visible on the index page. Any pending chargebacks will continue to be processed between the banks and gateways, but status updates on those chargebacks won't be persisted in Recurly.
What does 'lost' mean in the context of a Justt chargeback?
A chargeback with a lost status means the subscriber's dispute was upheld by their card issuer — the merchant lost the case. This is the status that triggers Recurly to take action (refund and/or expire) based on your configured settings.
Why do I need to recreate my API key when I re-enable the integration?
When you disable the Justt integration, Recurly invalidates the API key that was previously shared with Justt. This is a security measure to ensure a dormant key can't be used to access your Recurly data while the integration is inactive. When you re-enable, you'll need to create a fresh key and update it in your Justt account settings.
What's the difference between the 'Created' date and the 'Posting date' on the chargeback index?
The "Created" date reflects when Recurly received and recorded the chargeback event. The "Posting date" is the date the chargeback was formally reported to Justt by the card network — this comes directly from Justt's webhook payload and may be earlier than the created date in Recurly.
Updated about 1 hour ago