Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

core spec version 0.9.4: payment.collected_by has no type defined

Open
#414 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
52/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
yaml
Domain
api

Research direction

Open api/transaction/build/transaction.yaml at the payment.collected_by definition around line 1659. Confirm the field currently lacks a type, then define its type as string. Done means the specification explicitly declares payment.collected_by as a string.

Written by the indexing model from the issue text.

Description

Describe the bug
Defined here: https://github.com/beckn/protocol-specifications/blob/core-v1.1.0/api/transaction/build/transaction.yaml#L1659

It does not have a type defined.

Expected behavior
It should have a type, and it should be string.

Dominant language
No language data
Stars
453
Forks
127
PR merge metrics
No merged PRs in 30d

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from beckn/protocol-specifications

All issues in beckn/protocol-specifications

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.