docs: refresh sandbox verification suffix behavior - #912
Draft
jaymantri wants to merge 2 commits into
Draft
Conversation
Match the sandbox customer-verification behavior shipped in lightsparkdev/webdev: - #34311 Unregulated preset and the Skip verification paperwork switch - #34343 Business 003 resolves UNVERIFIED - #34357 Verification webhooks: IN_PROGRESS then one outcome event - #34451 Switch ON: businesses resolve from the suffix at create Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
|
The latest updates on your projects. Learn more about Vercel for GitHub. 2 Skipped Deployments
|
Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
mintlify/snippets/kyc/kyb-sandbox-suffixes.mdx003and001have no auto-decision and behave the same. New:001→PENDING,002→REJECTED,003→UNVERIFIED, other →APPROVED. Same mapping as individuals.POST /verificationsis needed.CUSTOMER.KYB_*only. It creates no verification and emits noVERIFICATION.*event.POST /verifications, aPATCHtoregistrationNumberre-derives the status while the business is not final.APPROVEDandREJECTEDare final.003onPOST /verificationsreturnsRESOLVE_ERRORSwithPOOR_QUALITY_DOCUMENT. Change the suffix and resubmit.mintlify/snippets/sandbox-verification.mdxPOST /verificationsemitsVERIFICATION.IN_PROGRESS, then oneVERIFICATION.<STATUS>event. The matchingCUSTOMER.KYC_*/CUSTOMER.KYB_*event fires when the status changes.CUSTOMER.KYC_*only, noVERIFICATION.*event. APATCHtofullNamebefore the first submission re-derives while not final.001and003both need a complete packet. New: with the switch off every suffix needs a complete packet; with the switch on,003resolves with no packet and001still needs one.003→UNVERIFIEDrow. A002owner rejects the business. A001registration number sets every ownerPENDINGwithout reading owner suffixes. Use003to test owners with the switch on.mintlify/snippets/kyc/kyc-unregulated.mdxmintlify/changelog.mdxCUSTOMER.KYB_*only. The older September sentence about businesses resolving at first submission now notes it was changed later that month.Why
003resolvesUNVERIFIEDIN_PROGRESSthen one outcome eventVerified against
webdev
origin/main:sparkcore/sparkcore/umaaas/grid_switches/umaaas/sandbox_grid_switch.pysparkcore/sparkcore/grid/api_handlers/sandbox_business_verification.pysparkcore/sparkcore/grid/api_handlers/sandbox_individual_verification.pysparkcore/sparkcore/grid/api_handlers/sandbox_verification_outcome.pysparkcore/sparkcore/grid/api_handlers/create_verification.pysparkcore/sparkcore/kyx/kyx_sandbox_manager.pysparkcore/sparkcore/ent/schema/grid/observers/ent_grid_customer_verification_webhook_observer.pymint broken-linksreports no broken links in the edited files. The 28 reported links are pre-existing in other files.