Detailed guidance on how to integrate Corrily with a payment gateway.
Braintree::WebhookNotification::Kind::SubscriptionCanceled
Braintree::WebhookNotification::Kind::SubscriptionExpired
Braintree::WebhookNotification::Kind::SubscriptionTrialEnded
Braintree::WebhookNotification::Kind::SubscriptionWentActive
Braintree::WebhookNotification::Kind::SubscriptionWentPastDue
Stripe’s value | Corrily’s value |
---|---|
incomplete | pending |
incomplete_expired | pending |
trialing | trialing |
active | active |
past_due | active |
canceled | canceled |
unpaid | canceled |
Chargebee’s value | Corrily’s value |
---|---|
future | pending |
in_trial | trialing |
active | active |
non_renewing | canceled |
paused | canceled |
canceled | canceled |
Chargebee’s value | Corrily’s value |
---|---|
future | pending |
in_trial | trialing |
active | active |
expired | canceled |
canceled | canceled |
Braintree’s value | Corrily’s value |
---|---|
Active | active |
Canceled | canceled |
Expired | canceled |
PastDue | active |
Pending | pending |
charge.captured
, charge.refunded
, charge.updated
, and charge.succeeded
events.type
). The transaction object contains the data that needs to be passed to Corrily.
Braintree::WebhookNotification::Kind::SubscriptionChargedSuccessfully
Braintree::WebhookNotification::Kind::SubscriptionChargedUnsuccessfully
Stipe’s value | Corrily’s value |
---|---|
draft | pending |
open | pending |
paid | succeeded |
uncollectible | failed |
void | failed |
Chargebee’s value | Corrily’s value |
---|---|
in_progress | pending |
success | succeeded |
voided | failed |
failure | failed |
timeout | failed |
needs_attention | failed |
Recurly’s value | Corrily’s value |
---|---|
pending | pending |
processing | pending |
success | succeeded |
chargeback | succeeded |
error | failed |
declined | failed |
Braintree’s value | Corrily’s value |
---|---|
Braintree::WebhookNotification::Kind::SubscriptionChargedSuccessfully | succeeded |
Braintree::WebhookNotification::Kind::SubscriptionChargedUnsuccessfully | failed |