BBMS declines

Options
Hi All,


Wondering if you guys had expereinced a larger than usually transaction declines by BBMS gateway for users coming from the same IP addresses due to IP blacklisting. If so, what's your approach to deal with this? The charlenge we are facing is that even if one person made a mistake when donating and triggers the IP blacklist, everyone in the same network will be black by BBMS for the next few hours/day which makes alot of our donor unhappy and difficult to react to it since the unblacking always have to happen on the BBMS end and is completely relying on their support.


Thanks!

Sam
Tagged:

Comments

  • Hi Sam,


    I've run into this issue a bit as well with our TeamRaiser events as we often have participants who are fundraising in the workplace. Compounding this is the fact that in order for us to know this is an issue, either the donor has to reach out to us directly at the organization or the donor reaches out to the participant who then reaches out to us and then it's been event longer by the time the technical staff can address this with BBMS. We tend to know the curve of when fundraising is active for our events, so we have been able to put a little bit of structure around resolving this. It's not ideal, but this is how we are currently working through it until BBMS makes some updates to lessen the severity of their existing rules.


    When we first launch our site, we run a declined transaction report that includes the Error code and IP address once a week. We sort the list by error code and then via the chat support in BBMS, we request the IP address that have been Blacklisted or blocked to IP declines rule to be white-listed.


    As we see donations pick up and we get closer to our event date and peak fundraising activity, we run a declined report more frequently and follow the same process of sorting and then submitting the blocked IP's to be approved. Like I said, it's not ideal, but it has helped a bit as we receive questions from donors or participants and sometimes we catch the block before a participant or donor does.


    - Karin

    Sam Li:

    Hi All,


    Wondering if you guys had expereinced a larger than usually transaction declines by BBMS gateway for users coming from the same IP addresses due to IP blacklisting. If so, what's your approach to deal with this? The charlenge we are facing is that even if one person made a mistake when donating and triggers the IP blacklist, everyone in the same network will be black by BBMS for the next few hours/day which makes alot of our donor unhappy and difficult to react to it since the unblacking always have to happen on the BBMS end and is completely relying on their support.


    Thanks!

    Sam

  • Thanks Karin, this is the kind of approaches we are going with as well. but as volume of donation picks up, this become harder and harder to manage.

    Also, our support team does not have direct chat/online portal access to BBMS which then we had to go through LO support -> BBMS support in order to get this resolved. Would you let me know who usually in your organization would contact BBMS?

    Sam



    Rockwin:

    Hi Sam,


    I've run into this issue a bit as well with our TeamRaiser events as we often have participants who are fundraising in the workplace. Compounding this is the fact that in order for us to know this is an issue, either the donor has to reach out to us directly at the organization or the donor reaches out to the participant who then reaches out to us and then it's been event longer by the time the technical staff can address this with BBMS. We tend to know the curve of when fundraising is active for our events, so we have been able to put a little bit of structure around resolving this. It's not ideal, but this is how we are currently working through it until BBMS makes some updates to lessen the severity of their existing rules.


    When we first launch our site, we run a declined transaction report that includes the Error code and IP address once a week. We sort the list by error code and then via the chat support in BBMS, we request the IP address that have been Blacklisted or blocked to IP declines rule to be white-listed.


    As we see donations pick up and we get closer to our event date and peak fundraising activity, we run a declined report more frequently and follow the same process of sorting and then submitting the blocked IP's to be approved. Like I said, it's not ideal, but it has helped a bit as we receive questions from donors or participants and sometimes we catch the block before a participant or donor does.


    - Karin

    Sam Li:

    Hi All,


    Wondering if you guys had expereinced a larger than usually transaction declines by BBMS gateway for users coming from the same IP addresses due to IP blacklisting. If so, what's your approach to deal with this? The charlenge we are facing is that even if one person made a mistake when donating and triggers the IP blacklist, everyone in the same network will be black by BBMS for the next few hours/day which makes alot of our donor unhappy and difficult to react to it since the unblacking always have to happen on the BBMS end and is completely relying on their support.


    Thanks!

    Sam

  • Hi Sam,


    I work with our finance team and the person who set up our BBMS account and I'm an admin on the LO side. So I access and a member of our Finance team are the people who can access our BBMS account to manage suspect or declined transactions.


    - Karin
  • Thanks!
  • Hi Karin


    How do you get the IP address in your report? I'm running the Declined Transactions report through BBMS but it doens't have that column.


    Thanks,

    Matt

  • I run the declined transactions report though the reports in Luminate Online. That report can include the the Error Code and the IP address.

  • Wonderful, thank you very much!


    Matt Tinker
    |
    Director
    ,
    Digital Innovation and Projects

    |

    Marketing and Communications
    __________________________________________________________________________________
    MSSociety
    of Canada | 500 - 250 Dundas Street West | Toronto, ON M5T
    2Z5

    Phone: 416-922-6065 x3176 | Fax: 416-922-7538 |
    Email: matt.tinker@mssociety.ca
    mssociety.ca |
    Find us on
    Facebook

  • Hi Matt, there should be error code and ip for u to include on report writer, under the transaction details report

Categories