There are never transactions when generating a sample webhook notification for SubscriptionChargedSuccessfully #64

Closed
oveddan opened this Issue May 30, 2014 · 1 comment

Comments

Projects
None yet
2 participants
@oveddan

oveddan commented May 30, 2014

Knowing how much the user was charged can be a key reason for consuming a webhook notification for SubscriptionChargedSuccessfully (i.e. tracking revenue per use internally).

When generating a sample webhook notification for this using Braintree::WebhookTesting - a subscription comes back with the webhook payload, but no transactions are ever a part of that webhook.

This subscription within the notification payload should contain a fake Transaction that includes a charged amount.

@raymondberg

This comment has been minimized.

Show comment Hide comment
@raymondberg

raymondberg Sep 14, 2015

This is basically a duplicate, but you're right that this would make things easier. We're going to push this in an upcoming release. Closing for now, but feel free to reopen if you still have questions after the new release.

This is basically a duplicate, but you're right that this would make things easier. We're going to push this in an upcoming release. Closing for now, but feel free to reopen if you still have questions after the new release.

crookedneighbor pushed a commit that referenced this issue Dec 26, 2017

Merge pull request #64 from braintree/core_0ySzQBjQ_allow_default_pay…
…ment_method_through_customer

core 0ySzQBjQ - Allow setting default payment method through Customer…
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment