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.

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

Add Fiserv contracts to MobiMart + minor copy update #519

Closed
mrose914 opened this issue Jan 25, 2024 · 5 comments · Fixed by #525
Closed

Add Fiserv contracts to MobiMart + minor copy update #519

mrose914 opened this issue Jan 25, 2024 · 5 comments · Fixed by #525
Assignees
Labels
content Simple wording or content updates

Comments

@mrose914
Copy link

mrose914 commented Jan 25, 2024

Requirements:

Add new row to Contracts > Payment Processors with the following columns:

  • Contract: 5-22-70-22-02
  • Category: Contactless Payment
  • Product: Payment Processor
  • Vendor: Fiserv*

Replace Elavon footnote with *, which should correspond to the same message below, which applies to both rows in the table.

*: "Available to California agencies only." to "Available to California agencies only. If you are an out of state agency, please reach out to [email protected] to discuss options."

@mrose914 mrose914 converted this from a draft issue Jan 25, 2024
@mrose914
Copy link
Author

@jenro1 let me know if this captures everything needed for the change.

@jenro1
Copy link

jenro1 commented Jan 26, 2024

This looks great, thanks Marissa! Is there a way to make the footnote apply to both Elavon and Fiserv, as it's the same situation for both? Perhaps an asterisk?

@mrose914
Copy link
Author

Ah, good to know! Yes I think we could asterisk each of them and use the same message.

Just out of curiosity, in the future, if we add more payment processor contracts, would they be likely to be the same? In other words, is the fact that payment processor contracts are available to CA agencies only something we expect for any future payment processor contract we add? If so, we could also add that as a blurb over the table to make it clear.

@thekaveman
Copy link
Member

@mrose914 @jenro1 is this content ready to go, can we begin working on this this week?

@mrose914
Copy link
Author

mrose914 commented Feb 5, 2024

@thekaveman yes, good to go!

@mrose914 mrose914 added the content Simple wording or content updates label Feb 6, 2024
@machikoyasuda machikoyasuda moved this from Todo to In Review in Digital Services Feb 8, 2024
@github-project-automation github-project-automation bot moved this from In Review to Done in Digital Services Feb 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content Simple wording or content updates
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

4 participants