Skip to main content

​
Real-World Example

ABC Collections submits Tilled merchant information and later receives a required-more-information request. The portal should show what is missing, collect the update, and keep payment setup blocked until the merchant path is safe.

​
Visual Flow

​
How It Should Work

  • It should keep merchant setup status clear to the creditor.
  • It should block payment processing until the selected gateway is configured and safe.
  • It should support required-more-information handling without losing the original application context.

​
How It Should Not Work

  • It should not let consumers pay through an incomplete merchant account.
  • It should not mix credentials between Authorize.net, Stripe, USAePay, and Tilled paths.
  • It should not hide provider errors that prevent payment readiness.

​
Developer Notes

  • Merchant setup affects consumer payment setup and background installment jobs.
  • Tilled account updates may arrive through background webhook jobs.
  • app/Livewire/Creditor/MerchantSettingsPage.php
  • app/Livewire/Creditor/TilledApplicationPage.php
  • app/Livewire/Creditor/RequiredMoreInformation.php
  • app/Livewire/Creditor/Forms/MerchantSettings/TilledForm.php
  • app/Jobs/ProcessTilledAccountUpdatedJob.php
  • app/Console/Commands/CreateTilledWebhookCommand.php
Last modified on May 25, 2026