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

The following property is either invalid or missing: streamline2_usd_terminal_id

Open
#24 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
ruby
Domain
api, payments

Research direction

Start with Samples/Payments/CoreServices/ProcessPayment.rb and inspect how merchantId, merchantKeyId, and merchantSecretKey are loaded into the transaction configuration. Reproduce the reported request error with valid credentials and compare the generated request with the API requirements. Done means the sample payment runs without the streamline2_usd_terminal_id invalid-or-missing error.

Written by the indexing model from the issue text.

Description

As soon as I change the merchantId, merchantKeyId, and merchantSecretKey in configuration transactions appear with the following error.

Running Samples/Payments/CoreServices/ProcessPayment.rb

{:code=>400, :response_headers=>{"Content-Type"=>"application/json", "Content-Length"=>"170", "X-Cnection"=>"close", "x-response-time"=>"290ms", "Strict-Transport-Security"=>"max-age=31536000", "v-c-correlation-id"=>"7079ce85-d3b1-423e-974e-79abacdde8f9"}, :response_body=>"{\"submitTimeUtc\":\"2019-10-09T17:27:37Z\",\"status\":\"INVALID_REQUEST\",\"reason\":\"INVALID_DATA\",\"message\":\"Declined - One or more fields in the request contains invalid data\"}"}

Screen Shot 2019-10-09 at 9 44 01 PM
Dominant language
Ruby
Stars
1
Forks
13
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: 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.

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.