/
API Troubleshooting & Training

API Troubleshooting & Training

Owned by Tiffany Rapp
Aug 27, 2024
3 min read

UAT Testing notes/highlights:

  • Mockup various hierarchies and clients/programs you want to learn more about or want to test.  

    • ClientIDs are created in FIS UAT

    • Can add fake $ via FIS CSA UAT

    • Physical cards will not create so you cannot view card carriers/images but you can test the process (account creation).

    • Digital cards will create - can receive Emails and SMS and walk through the cardholder redemption process (MyDashCard UAT, dash.digital UAT, card-support UAT)

 

  • Bulk ordering does NOT work in UAT.

    • Single Payment product is the only thing you can test end to end.

    • Full Reward flow does not work in UAT bc everything is batch/bulk and that is not supported by FIS in UAT.

      • So your Reward clients (if using true Reward product) will need to 'test' in Production.

 

  • Ensure the product/program you configure for a client in UAT closely, if not exactly, matches what they will use in Production. 

    • Work with Product team to add new UAT Products as needed.

 

  • Your basic FT clients will likely not need UAT.  This will mainly be for your API clients.  

    • But YOU can and should test in UAT often!  The Product Release notes are a great place to start - if something new is released and you know you have a client waiting on it or you work with that product often, go test it!

 

  • Before telling the client to go test - confirm what you are asking them to test WORKS!

    • This allows us to catch the errors and/or gaps prior to the client.

    • Notify Abby when you find these gaps so I can work with Product/Engineering to identify flaws in the product rollout process.

      • It is not up to you to test functionality.  But it IS up to you to ensure what you set up for a client works how we believe it to work.  If it doesn't and we followed all proper instructions for setup, then it is a Product/Engineering issue.  The more examples I have, the more I can work to get these resolved and better testing done by our Product/Engineering teams.

      • Ask them for API/FTP samples!  If they have tested the product/feature for completion and success, I assume they should have! 🙂

    •  

PROD Testing notes/highlights:

  • Create a "Test" environment for yourself in Production or leverage the ABC Test Company group.

    • These are REAL cards, funds, clients. Cards WILL create, ship, load, etc.

      • Keep loads and orders small but know that you 100% can test in Production and should be testing in Production for some of these bigger clients and new features.

 

  • Order yourself and/or the client a test card to ensure the following:

    • The program is setup correctly.

    • The card image/carrier is correct.

    • The email/sms is configured correctly and is what they client wants.

    • Confirm the email/sms sends!

    • Confirm the redemption process - we must improve in this area!  Make sure you know how the cardholder activates and their experience and that the client knows/understands this and agrees to it!

    • Reporting is processing as expected - VFA history, digital reporting, value loads, MCR, etc.

 

  • If you are having a client test in Production, make sure they know they are in Production!

    • Monitor their tests - immediately jump in if you see large loads, orders.

    • Cards WILL create, load, ship, etc.

      • Keep orders and loads small.

    • You may load $20.00 for testing to their VFA.  This is real $ and Abby can tell you how to load this and account for the funds in CSA.

    • Full end-to-end FTP testing must always be in Production

      • Hopefully a new process is coming, but bulk/batch is an FIS limitation in UAT.

    •  

  • Before telling the client to go test - confirm what you are asking them to test WORKS!

    • This allows us to catch the errors and/or gaps prior to the client.

    • Notify Abby when you find these gaps so I can work with Product/Engineering to identify flaws in the product rollout process.

      • It is not up to you to test functionality.  But it IS up to you to ensure what you set up for a client works how we believe it to work.  If it doesn't and we followed all proper instructions for setup, then it is a Product/Engineering issue.  The more examples I have, the more I can work to get these resolved and better testing done by our Product/Engineering teams.

      • Ask them for API/FTP samples!  If they have tested the product/feature for completion and success, I assume they should have! 🙂