zai_payment 2.0.0 → 2.0.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 969c7fa3deee862ffafc7513c766c7977c0ea7d8c150b86ed0b69d6b271fb4f2
-  data.tar.gz: ab0be12da8a64a0e0542679bd7120ff344007d63ad1a259e645a267b7e32559c
+  metadata.gz: de2e744f1102ac7982d84422f7381d5c4928bd2afc1e2c2104946dbe57ebbb15
+  data.tar.gz: d00b49b1354c78899ead062c890fb4bfeab0057d82df45d88ff64a66916f6119
 SHA512:
-  metadata.gz: b75eac297840e7290ec04ef31bf0983b658758b72e98a181dfc43e136c72d631a276570509bbd3b8f22c18b7dd09f3753f42dac047985dfa8665a643f29b03ab
-  data.tar.gz: 131560ea7a36ebf84948df973c71a688fe86ae2ad9d3adf93598cf75366b615163957a5cdcef27f739962ec3a2b682ad3c1e7b2150cb9d356e133a4cd270bbad
+  metadata.gz: ba4b187933438167c31b91fbaa42372d285861e0cb5b806dddde7d9f1cb2b2986ee0477d341ffecff033a85c104abe3b13636afc4979f46855c20d8e6a1c6d9d
+  data.tar.gz: 2d12d31b7e02a9b24169bae9fddacb1b61bd3dec45e210bdea5ddaf6343533f8269184de881f77f25c3dab610f13e82c7bdfa157e506ad792d903e328c574427

data/.yardopts

@@ -1,3 +1,3 @@
 --markup markdown
---readme README.md
+--readme readme.md
 lib

data/badges/coverage.json

@@ -1 +1 @@
-{"schemaVersion": 1, "label": "coverage", "message": "94.77%", "color": "brightgreen"}
+{"schemaVersion": 1, "label": "coverage", "message": "95.19%", "color": "brightgreen"}

data/changelog.md

@@ -1,4 +1,14 @@
 ## [Released]
+## [2.0.2] - 2025-10-24
+### Fixed
+- **Items API**: Fixed endpoint configuration to use `core_base` instead of `va_base`
+  - Items resource now correctly uses the `https://test.api.promisepay.com` endpoint (prelive) 
+  - Resolves CloudFront 403 error when creating items via POST requests
+  - Ensures Items API uses the same endpoint as Users API for consistency
+
+## [2.0.1] - 2025-10-24
+### Changes
+  - Updated markdown files
 
 ## [2.0.0] - 2025-10-24
 ### Added
@@ -20,10 +30,25 @@
 - Full RSpec test suite for Items resource with 100% coverage
 - Comprehensive examples documentation in `examples/items.md`
 
+### Changed
+- **User Management Enhancement**: Updated user creation validation to support user type-specific required fields
+  - `user_type` parameter now determines which fields are required during user creation
+  - Payin users require: `email`, `first_name`, `last_name`, `country`
+  - Payout users require additional fields: `address_line1`, `city`, `state`, `zip`, `dob`
+  - Company validation now enforces required fields based on user type
+  - For payout companies, additional fields required: `address_line1`, `city`, `state`, `zip`, `phone`, `country`
+  - All companies require: `name`, `legal_name`, `tax_number`, `business_email`, `country`
+- **Clarified device_id and ip_address requirements**: These fields are NOT required when creating a payin user, but become required when creating an item and charging a card
+- Refactored company validation logic for better maintainability and reduced cyclomatic complexity
+
 ### Documentation
 - Added detailed Items API examples with complete workflow demonstrations
 - Payment types documentation (1-7: Direct Debit, Credit Card, Bank Transfer, Wallet, BPay, PayPal, Other)
 - Error handling examples for Items operations
+- Updated User Management documentation (`docs/users.md`) with correct required fields for each user type
+- Updated all user examples in `examples/users.md` to reflect proper user type usage
+- Added clear notes about when `device_id` and `ip_address` are required
+- Updated company field requirements in all documentation
 
 **Full Changelog**: https://github.com/Sentia/zai-payment/compare/v1.3.2...v2.0.0
 
@@ -33,7 +58,7 @@
 - Added `yard` gem as development dependency for API documentation
 
 ### Fixed
-- Fixed YARD link resolution warning in README.md by converting markdown link to HTML format
+- Fixed YARD link resolution warning in readme.md by converting markdown link to HTML format
 
 ### Documentation
 - Configured YARD to generate comprehensive API documentation

data/contributing.md

@@ -231,7 +231,7 @@ feat(webhooks): add support for webhook signature verification
 
 fix(auth): prevent token refresh race condition
 
-docs: update README with webhook examples
+docs: update readme with webhook examples
 
 test(client): add specs for error handling
 ```
@@ -364,7 +364,7 @@ end
 ### Recognition
 
 Contributors will be recognized in:
-- The project's README (if significant contribution)
+- The project's readme (if significant contribution)
 - The CHANGELOG for their specific contributions
 - Release notes
 

data/docs/webhook_signature.md

@@ -60,7 +60,7 @@ Test categories:
 ### 4. Documentation
 
 #### Updated Files:
-1. **`docs/WEBHOOKS.md`** (170+ lines added)
+1. **`docs/webhooks.md`** (170+ lines added)
    - Complete security section
    - Step-by-step setup guide
    - Rails controller examples
@@ -77,7 +77,7 @@ Test categories:
    - Background job processing pattern
    - Idempotency pattern
 
-3. **`README.md`** (40+ lines added)
+3. **`readme.md`** (40+ lines added)
    - Quick start guide
    - Security features highlights
    - Simple usage example

data/implementation.md

@@ -110,7 +110,7 @@ Practical examples including:
 - RSpec integration tests
 - Common patterns with retry logic
 
-#### README Updates (`readme.md`)
+#### readme Updates (`readme.md`)
 - Added Users section with quick examples
 - Updated roadmap to mark Users as "Done"
 - Added documentation links
@@ -149,7 +149,7 @@ response = ZaiPayment.users.create(
   first_name: 'Jane',
   last_name: 'Smith',
   country: 'AUS',
-  dob: '19900101',
+  dob: '01/01/1990',
   address_line1: '456 Market St',
   city: 'Sydney',
   state: 'NSW',
@@ -208,7 +208,7 @@ response = ZaiPayment.users.update(
 
 1. **Email**: Must be valid email format
 2. **Country**: Must be 3-letter ISO 3166-1 alpha-3 code (e.g., USA, AUS, GBR)
-3. **Date of Birth**: Must be DD/MM/YYYY format (e.g., 19900101)
+3. **Date of Birth**: Must be DD/MM/YYYY format (e.g., 01/01/1990)
 4. **User Type**: Must be 'payin' or 'payout' (optional field)
 
 ## Error Handling

data/implementation_summary.md

@@ -169,8 +169,8 @@ The following documentation files have been updated:
 
 1. **`lib/zai_payment/resources/user.rb`** - Implementation
 2. **`examples/users.md`** - Usage examples and patterns
-3. **`docs/USERS.md`** - Field reference and comprehensive guide
-4. **`README.md`** - Quick start example
+3. **`docs/users.md`** - Field reference and comprehensive guide
+4. **`readme.md`** - Quick start example
 
 ## Testing
 
@@ -190,6 +190,6 @@ These changes are **backward compatible**. All new parameters are optional and e
 
 - `/lib/zai_payment/resources/user.rb` - Main implementation
 - `/examples/users.md` - Usage examples
-- `/docs/USERS.md` - Field reference
-- `/README.md` - Quick start guide
+- `/docs/users.md` - Field reference
+- `/readme.md` - Quick start guide
 

data/lib/zai_payment/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module ZaiPayment
-  VERSION = '2.0.0'
+  VERSION = '2.0.2'
 end

data/lib/zai_payment.rb

@@ -49,7 +49,7 @@ module ZaiPayment
 
     # @return [ZaiPayment::Resources::Item] item resource instance
     def items
-      @items ||= Resources::Item.new
+      @items ||= Resources::Item.new(client: Client.new(base_endpoint: :core_base))
     end
   end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: zai_payment
 version: !ruby/object:Gem::Version
-  version: 2.0.0
+  version: 2.0.2
 platform: ruby
 authors:
 - Eddy Jaga
@@ -102,8 +102,8 @@ metadata:
   allowed_push_host: https://rubygems.org
   homepage_uri: https://github.com/Sentia/zai-payment
   source_code_uri: https://github.com/Sentia/zai-payment
-  changelog_uri: https://github.com/Sentia/zai-payment/blob/main/CHANGELOG.md
-  code_of_conduct_uri: https://github.com/Sentia/zai-payment/blob/main/CODE_OF_CONDUCT.md
+  changelog_uri: https://github.com/Sentia/zai-payment/blob/main/changelog.md
+  code_of_conduct_uri: https://github.com/Sentia/zai-payment/blob/main/code_of_conduct.md
   rubygems_mfa_required: 'true'
   documentation_uri: https://github.com/Sentia/zai-payment#readme
 rdoc_options: []