#bhanu365

1 messages · Page 1 of 1 (latest)

alpine shellBOT
thorn sonnet
#

Are you seeing this applied to a second actual invoice, currently?

#

Or only the upcoming invoice view?

plush kayak
#

on upcoming invoice

thorn sonnet
#

Gotcha -- can you share the specific invoice where this was used first? (or subscription)

plush kayak
#

in_1M4rcQFmM52WOkSotTatQl5f

#

?

#

Hey there?

thorn sonnet
#

hey sorry, lots of folks online

#

looking at that

meager light
#

Hello, synthrider has to step out soon but I am taking a look. Will get back to you with what I can find

plush kayak
#

ok I am waiting

thorn sonnet
#

hey there sorry this was tricky to understand, but i can share what i've figure out before stepping away

#

So i think this is not actually the coupon discounting twice, it looks like you're re-using a single test customer with multiple invoices/subs, and making changes that produce a customer balance

#

the customer balance is discounting that first invoice to $0, not the coupon

#

and we don't want to "waste" the coupon on a $0 invoice, so it applies to the next one

#

My suggestion is: create a new customer for testing your coupon flow

#

This will keep things a lot simpler and avoid any customer balance credits confusing the invoice amount

plush kayak
#

ahh got it

#

You are right

#

let me check with new customer

thorn sonnet
#

Especially if you're manipulating discounts and updating/cancelling subscriptions with prorations, you'll get all kinds of customer credit floating around

#

a new customer for a new test sequence is the way to go

plush kayak
#

the same issue occurs with a new customer as well

meager light
#

Can you send the ID for that invoice as well?

plush kayak
#

in_1M4tDEFmM52WOkSoLW38ZMlM