Sandbox - Cont. in payment issue
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
When testing the Cont. in filing in sandbox, we found auto approval worked, but got error response from Pay-API.
Investigate this issue and see if it's on our side missed anything in the payload, or maybe better notify Pay team.
Error log from business-api-sandbox:

Error log from pay-api-sandbox:

Error response when directly calling pay-api-sandbox endpoint:
Endpoint: {{sandbox_pay}}/api/v1/payment-requests
Payload:
```JSON
{
"businessInfo": {
"businessIdentifier": "TS2W5U8rxF",
"corpType": "C",
"businessName": "TS2W5U8rxF",
"contactInfo": {
"city": "mailing_address city",
"postalCode": "H0H 0H0",
"province": "BC",
"addressLine1": "mailing_address - address line one",
"country": "CA"
}
},
"filingInfo": {
"filingIdentifier": "1627342",
"filingTypes": [
{
"filingTypeCode": "CONTI",
"futureEffective": false,
"priority": false,
"waiveFees": false
}
]
},
"details": []
}
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the /api/v1/payment-requests sandbox endpoint and compare the provided payload with the business-api and pay-api error logs. Determine whether the request is missing or misformatting data on this side, or whether Pay must handle the response. Done means the cause and responsible team are documented, with a fix or Pay-team notification identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- flask, javascript, python
- Domain
- api, backend, payments
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100