Information on creating a PayFac ticket to send to the PayFac support team. This will give instructions, and best practices to create a ticket with all the information that is needed to investigate and correct issues with the Portal, payments, payouts, etc.
Allot of issues can be resolved by posting the question/request in one of the Slack support channels. If it isn’t able to be resolved there you will be directed to open a PayFac support ticket.
Link for support teams to enter a ticket:
https://payfac.quiltsoftware.com/support/home
https://payfac.quiltsoftware.com/support/home
<aside> 💡
Note: Use the Login/Sign up to sign into the ticket system to have your email entered and receive the follow up messages sent from the support team. You can also enter a ticket without signing in, and the emails will be sent to a generic support email address for your support team.
</aside>
Follow the steps below to create a ticket to the PayFac support team. The required fields are: Brand, MID, Agent Name, Support Email Address, Subject, and Comment.
Using the drop down, select the option for PayFac Support.
Use the drop down to select the Brand this merchant falls under.
Select the processor (Stripe or Adyen).
What type of terminal is in use.
The issue type.
Priority of the issue (Typically will be low unless issue impacting multiple merchants).
Severity of the issue (Indicate if this is a work stoppage event, or just a cosmetic issue the merchant wants corrected).
<aside> 💡
Note: Adyen MID’s begin with a BA, and Stripe begin with acct_.
</aside>
<aside> 💡
Note: Sign the bottom of the comment with your name as it appears in Slack and the PayFac support team member will reach out directly to you with any questions for clarification.
</aside>
Submit the ticket. You will get a message back letting you know the issue has been received from the ticket system. If the ticket was submitted between the hours of 7am and 4pm MST you will most likely receive a reply letting you know the issue is being worked on, resolved, sent to the Dev team, have follow up questions, or give instructions to correct the reported problem within an hour or two. If outside the indicated hours your reply will fall into the next business day.
Below are some best practice tips.