-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix: Change network value from mainnet to regtest #26
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Think network should come from PayD - possibly from the destinations endpoint
service/paymentrequest.go
Outdated
@@ -51,7 +53,7 @@ func (p *paymentRequest) CreatePaymentRequest(ctx context.Context, args p4.Payme | |||
// here we store paymentRef in extended data to allow some validation in payment flow | |||
merchant.ExtendedData["paymentReference"] = args.PaymentID | |||
return &p4.PaymentRequest{ | |||
Network: "mainnet", | |||
Network: string(p.deployCfg.Network), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should probably come from payd actually rather than being set on P4, this has been something on my internal backlog to fix but hadn't got round to it yet.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So should payd be dumb to the network it's running against as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Currently in testing the payment body says
"network": "mainnet"
on regtest.