nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Power Automate - Send an HTTP Request for Payments API

Matt Thacker

I seem to recall when the announcement of the Send an HTTP Request action was first sent out, there was a note that it would work with all API endpoints except the Payments API, but I can't find that language now. Is this still the case? (I'm assuming so because it get an “invalid subscription key” when I try to send a request)

I'm trying to use the Automate Recurring Gift endpoint, but the POST request requires the following in the body of the request:

{
"bbps_configuration_id": "string",
"account_token": "string"
}

Is there a way to get the BBPS Configuration ID and Account Token for the account without using the Payments API?

Find more posts tagged with

Microsoft Power Platform

Comments

Glen Hutson

@Matt Thacker
My understanding (and my colleagues can correct me if I'm mistaken) is that the reason why Blackbaud doesn't touch the Payments API via Power Automate is due to any PCI implications that may need to be considered. Along with that would be why the Automate Recurring Gifts endpoint isn't part of the RENXT Connectors.

That being said, one could get both the BBPS configuration and a token via the Developer Console. However, with the token having an expiration, that wouldn't work for a automatic recurring process, but may help facilitate some scenarios.

Ben Lambert

Hi Matt, @Glen Hutson is correct. The Payments SKY API is not amongst the SKY APIs that the Power Platform connector(s) are able to call. Primarily this was to simplify things for our initial forage into Power Platform connectors (and avoid complex discussions about PCI concerns).

So there's no “technical” reason, it's just a policy for now. That is certainly something we can reevaluate (especially given a real-world use case). So please make sure to get this idea documented in the Ideas portal as it will help the team understand the need going forward. For example, another option we could consider is allowing calls to the non-PCI-concerning endpoints in the Payments SKY API as a happy middle ground.

12th Floor Development

@Glen Hutson @Matt Thacker

I know this conversation is two years old, but do either of you know if there has been any updates to the Power Platform SKI Add connector to allow calls to the Payments API? We're trying to finalize a BB checkout transaction from a Power App but I'm getting 401 unauthorized on the call.

Erik Leaver

Hi @12th Floor Development there still isn't a method to make calls to the Power Platform connector but we are in active research. If you can send your business case to me, that will help. bbdevdays@blackbaud.com

12th Floor Development

Hi @Erik Leaver ,

Thanks for the quick response. We are building a Power App to let internal (authorized) staff submit simplified gifts (using the gifts endpoint on the SKY Add in connector). Part of this form is entering Credit Card or Debit info. Once an assigned approver, approves the submission, then the gift should be created and the payment transaction completed.

Ideally, we have a link/button on the Power App form to open the BB checkout interface and allow the internal user to enter the payment details (which we can do using an approach that aligns with your BB checkout best practice), but there is no way of finalizing the payment transaction from within the Power App when the form submission is approved. We can create the gift, but the transaction is left in a Not Processed state because we have no way of finalizing this payment. We're stuck unless we create a completely different app to finalize transactions.

If there is another alternative, let me know!

Erik Leaver

@12th Floor Development - thanks for the info. I'll pass it along to our team. No timeline is set for this functionality but as noted, we are researching.

If others have similar needs, please add to the thread so I can add to the business case!

Dan Snyder

@Erik Leaver For easier reconciliation with our business office, we have been recording merchant fees as a custom field on gift records. Currently we are just using a formula in a Power Automate flow to do this, but if the fee structure changes it would be great if we could just call the transaction directly to get the total fees.

Erik Leaver

@Dan Snyder Understood. I'll flag to the right people!

Erik Leaver

@Dan Snyder Could you use the Transaction API to get the fees? See: https://developer.sky.blackbaud.com/api#api=payments&operation=GetTransaction "total_fees"

Dan Snyder

https://community.blackbaud.com/discussion/comment/308464#Comment_308464

That is what I was trying to use and got a 401 error in Power Automate. I have all permissions on the account I am using to connect, and it works in Try It.

Is it because there are two API subscriptions (Standard and Payments), but the SKY Add-Ins connector is only looking at Standard?

Erik Leaver

@Dan Snyder Argh. I forgot that api doesn't work in Power Automate. Let me see what I can do.

Dan Snyder

Thanks @Erik Leaver.