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; } } }

Card Tokenization

Lauren White

Hello,

When working with the Blackbaud checkout payment form, it requires a guid as the card_token property to tell Blackbaud to tokenize the credit card for future charges (a recurring giving scenario).

6d78afd2d855b1d598c5022d5b430981-huge-sc

Why does it require this uuid in the JavaScript when the payments api checkout transaction endpoint returns a different guid as the card token upon a successful transaction?

c1f2e8d03e2894ac4b7ae61d33963043-huge-sc

Am I missing something here?

Thanks!

Find more posts tagged with

Comments

Mina Mistry

Hi Lauren

The token that you generate and use in the JavaScript will represent the card details that get saved for future payments.

When calling the Capture endpoint for that transaction, the same token should be returned in the response object.

Is the problem that you are seeing a different token coming back from the Checkout Capture endpoint, or are you seeing zeros?

Lauren White

@Mina Mistry Apologies, Mina. Thank you for your response! Upon further testing, it appears to be returning the same uuid as the JavaScript.

As a follow up question, why does Blackbaud require that we provide a uuid in the JavaScript rather than simply passing a property of ‘true’ with the card_token to instruct Blackbaud to tokenize the card? Why make the client provide the uuid?