Skip to content

feat(schema): COMCORE-5156 add collection target to payment action schema - #293

Open
sgopalan-godaddy wants to merge 1 commit into
mainfrom
COMCORE-5156
Open

sgopalan-godaddy wants to merge 1 commit into
mainfrom
COMCORE-5156

Conversation

@sgopalan-godaddy

Copy link
Copy Markdown
Collaborator

https://godaddy-corp.atlassian.net/browse/COMCORE-5156

  • collectionEntityTargetId will be passed to GPA to drive a specific outcome based on that. When a caller supplies collectionEntityTargetId, the GPA creates a Commerce Payment Request, and Payment Requests uses Payment Bridge to present the payment on the selected Poynt terminal.
  • GPA work https://github.com/gdcorp-commerce/commerce-gpas/pull/134

Copilot AI lite review requested due to automatic review settings September 25, 2026 16:25
@sgopalan-godaddy sgopalan-godaddy changed the title COMCORE-5156 add collection target to payment action schema feat(schema): COMCORE-5156 add collection target to payment action schema Sep 25, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot review overview

🟡 Changes recommended

Anchor the schema pattern so invalid prefixed or suffixed IDs are rejected.

Get a fresh assessment by requesting another Copilot review.

Review effort: Lite
Findings: 1 Medium severity

Open (1)
What changed in this PR

Adds optional collectionEntityTargetId support to the commerce payment action schema for terminal-directed payments.

Changes:

  • Adds a reusable ID definition and optional collection target property.
  • Adds schema tests for optionality and accepted ID formats.
File Description
rust/​src/​platform/​actions/​mod.rs Tests the new schema field and ID formats.
rust/​schemas/​actions/​commerce-payment-process.json Defines collectionEntityTargetId and its ID schema.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

"$schema": "https://json-schema.org/draft/2020-12/schema",
"description": "Custom ID format that can take a URN or a UUID",
"example": "urn:tid:oak:410dee2e-abbf-3f59-b640-fc3aca175344",
"pattern": "([0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12})|(urn:[a-z]{1,3}:[a-z]{1,3}:[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12})",
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants