Currently, port-out PINs require manual intervention from support. This
command allows customers to self-manage their port-out PINs. Actual
functionality is delegated to the user's backend. For now, that's just
sgx-bwmsgsv2.
References: https://todo.sr.ht/~singpolyma/soprani.ca/380
2a30a46
Merge branch 'fix/change-number-for-unregistered' of git.sr.ht:~phdavis1027/sgx-jmp
Click to expand commit body
* 'fix/change-number-for-unregistered' of git.sr.ht:~phdavis1027/sgx-jmp:
NumberChange can now handle unregistered cust
Stephen Paul Weber
created
4ccca7d
NumberChange can now handle unregistered cust
Click to expand commit body
- old_tel is nil if customer unregistered
- test unregistered for blank num
^ involved fixing a race between check_noop and check_orphan
act on feedback
Phillip Davis
created
bcc97a3
use tn.get_details[:city] in stash_for_later
Click to expand commit body
i apparently thought this was broken earlier, but it seems to just
work in test cases i have tried, so let's see if this version just does
what it should
* premium:
Factor out BuyNumber
Inject price
Bill after charge
Inline useless methods
Remove unused method
Fix test
charge for premium nums
refactor registration_test to use real Tn's
two changes related to registration forms
price functionality on Tns
Remove legacy card charge behaviour
two fixes related to eSIM nicks:
Factor out reload customer, check balance, maybe bill
Unify more invite code handling
Remove mostly-unused final_message
Remove legacy card charge behaviour
We used to have them add card in web then charge after, but these days
we charge them in web for this first tx to get 3DS, so this code path is
all but dead and we can remove it.
Using the optional field on Activation or the InviteCode flow now use
the same code and do the same things. Always check balance and proceed
to bill if we've used a parent code, otherwise never do that.
Fixes the subaccount-from-onboarding guard as well.
Was only being used for PayPal transitions (which are mostly done) and
only when transitioning to BTC (which they usually don't) and only
provided extra reinforcement of a message they've already seen by now.
Let's not complicate the code for that.
We used to have them add card in web then charge after, but these days
we charge them in web for this first tx to get 3DS, so this code path is
all but dead and we can remove it.