Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Configure a payment-processor per agency #1364

Closed
thekaveman opened this issue Apr 17, 2023 · 0 comments · Fixed by #1365
Closed

Configure a payment-processor per agency #1364

thekaveman opened this issue Apr 17, 2023 · 0 comments · Fixed by #1365
Assignees
@thekaveman
Labels
bug Something isn't working

Comments

@thekaveman
Copy link
Member

Right now in the data migration, we have a single PaymentProcessor definition that is reused for both agency definitions.

Let's create a second PaymentProcessor so that we can have different configuration per-agency.

Ultimately will be solved by #1313 and related work.

Expected behavior

We should be able to vary the configuration between different agencies.

Additional context

See Slack thread.
@thekaveman thekaveman added the bug Something isn't working label Apr 17, 2023
@thekaveman thekaveman self-assigned this Apr 17, 2023
@thekaveman thekaveman mentioned this issue Apr 18, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@thekaveman thekaveman

Labels
bug Something isn't working
Projects
Digital Services
Status: Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Feat: Configure a payment processor for SacRT cal-itp/benefits
1 participant
@thekaveman