Documentation Index
Fetch the complete documentation index at: https://docs.younegotiate.com/llms.txt
Use this file to discover all available pages before exploring further.
Real-World Example
Jane accepts a settlement and enters a debit card. The portal should use the creditor’s configured merchant gateway, store or use the payment method safely, and only create the schedule once payment setup succeeds.Visual Flow
How It Should Work
- It should use the creditor merchant setup and supported payment gateway.
- It should support saved wallet methods when allowed.
- It should create or update payment setup only after payment method validation succeeds.
- It should move the account into the right scheduled or payment-plan status.
How It Should Not Work
- It should not store sensitive payment details outside the approved payment profile flow.
- It should not schedule payments when merchant setup is missing or invalid.
- It should not confuse one-time settlement setup with installment plan setup.
Developer Notes
- Payment setup connects consumer UI, payment profiles, merchant services, and schedule transactions.
- Gateway-specific behavior should remain behind the existing service/job layers.
Related App Areas
app/Livewire/Consumer/Payment.phpapp/Livewire/Consumer/Forms/PaymentForm.phpapp/Services/Consumer/PaymentProfileCreationService.phpapp/Services/Consumer/PaymentSetupCompletionService.php