Your distribution doesn't appear to be in a VCS. I wanted to create a pull/merge request, but to no avail, and I really don't feel like creating and sending patches so I'll just give some feedback on Business::Stripe::Webhook.

• There's no need to eval $VERSION: $VERSION = eval $VERSION;
• It is best common practice to absorb your parameters in a list. Instead of my $class = shift;, you should be doing my ($class) = @_;
• Reduce a ton of noise by eliminating quotes in hash keys when they don't contain anything other than alphanum and underscore. This: $vars{'error'} becomes this: $vars{error}
• Why are you doing an eval on this line... you do nothing at all if eval fails: $vars{'webhook'} = eval { decode_json($vars{'payload'});};
• Most of your comments are superfluous... the ones before each sub are unneeded. Your sub name should exactly state what it's doing; in your case, they do... remove the comments. Use comments to explain WHY something is happening, not what is happening.
• No need for this: $self->{'error'} = '';. It'll be autovivified if needed.
• Avoid returning throughout an entire subroutine. It makes it very hard for a reader to see what's happening (there are other reasons, but this is a big one). Instead of a bunch of return undef; inside of many if/else statements, create a flag at the top of the sub, and have each if/else set it. Return at the end of the sub.
• This is pedantic, but you only need the dereference operator after the first instance of a reference in a chain. This $self->{'webhook'}->{'type'}; can be written as $self->{webhook}{type};. Again, reduces noise.
• You can interpolate hash values. Instead of my $signed_payload = $sig_head{'t'} . '.' . $self->{'payload'};, you can simply do: my $signed_payload = "$sig_head{t}.$self->{payload}";
• Touching on an above topic, this: my $self = shift; my %keys = @_; is better written as my ($self, %keys) = @_;
• There's no need for a return; at the end of a sub if nothing's being returned (unless you intentionally are returning undef;

There's some other oddity (don't have the time to figure out why you're using STDOUT and STDERR instead of just using available built-ins, nor can I sort out at a glance why you're using the & for certain calls. However, hopefully you find some use in my quick code review here.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.