Payment Configuration ID

Vivian Nash
Vivian Nash
in SKY Developer General Discussions

Hi,

I am a SKY Developer Cohort member testing the New Checkout modal integration. I have:

  • Application ID: 3061735b-6fe7-4814-8cc1-d12d6cf400d8
  • Payment Configuration ID: 19761b45-9295-4a5c-aa26-c754200cd90f (retrieved via GET /paymentconfigurations)
  • Test domain: https://treelife.bluelemonmedia.com

When I use the sample modal code from your documentation, I get:

  1. GET /uicfg/settings/user 404
  2. "Can't process your payment due to a problem with the form's payment configuration"

My questions:

  1. Is 19761b45-9295-4a5c-aa26-c754200cd90f the correct paymentConfigurationId for cohort testing?
  2. Does my domain need to be whitelisted for this configuration?
  3. Does the New Checkout modal support anonymous (non-logged-in) donors?

Thank you

Answers

  • Bob Raymond
    Bob Raymond
    Sixth Anniversary Kudos 1 Name Dropper Facilitator 1
    1. I have this working. I use a payment configuration ID from here https://developer.sky.blackbaud.com/api#api=payments&operation=ListPaymentConfiguration. I picked one that I set up as a test
    2. Not as far as I'm aware
    3. Yes

    here's the snippet I use to initialize:

    var checkoutService = null;
    document.addEventListener('bbcheckout-loaded', () => {
    initializePaymentsCheckoutService();
    });

    1. function initializePaymentsCheckoutService() {
      let checkoutConfiguration = {
      paymentConfigurationId: 'xx', //test from list in #1
      feeOffsetType: 0,
      paymentMethodOptions: {
      wallets: {
      applePayEnabled: true,
      googlePayEnabled: true,
      },
      },
      workflowMode: 'modal',
      languageLocale: 'en-US',
      primaryColor: '#30ABBB',
      };
      checkoutService = window.BlackbaudCheckout(checkoutConfiguration);

      checkoutService.checkoutComplete.subscribe((e) => {
      // handle Complete event
      if (e.success) {
      …
      }
      })
      checkoutService.checkoutModal.ready.subscribe((e) => {
      …
      });
      checkoutService.checkoutModal.canceled.subscribe((e) => {
      …
      }
  • Bryce Howard
    Bryce Howard
    Fourth Anniversary First Reply Kudos 1 Name Dropper

    1. Probably. If you retrieved it via /payments/v1/paymentconfigurations using an oauth token authorized against the sandbox env you're using. The id is env scoped, so if the token came from a different env than the one checkout is loading against, it will fail with exactly the error you're seeing.
    2. Depends. The redirect uri list in your sky app registration is a separate thing and is used for oauth callbacks.
    3. The donor doesn't have to log in, but the integrator side still requires server-side oauth before the browser ever uses the blackbaud checkout modal (the iframe payment overlay that pops up when a donor clicks donate/pay on a form) Your server gets a sky api access token, validates the transaction, and it's opened with merchant/public-key parameters. The /uicfg/settings/user 404 is a symptom that the modal is initializing without the context it needs which can happen if:
      1. The required public key from /payments/v1/publickey wasn't passed into Blackbaud_OpenPaymentForm
      2. The merchant account id wasn't included with the payment config id
      3. The page isn't being served through a valid sky api session

Categories