Tokenized Transactions

Tokens let SAP access transactions created in a consumer application that is directly connected with BlueSnap. For instance, you may process a transaction in your e-Commerce platform and then need to refund it through SAP. When this occurs, SAP DPA checks that the transaction exists with BlueSnap and matches the data provided.

For more information, refer to Direct Connection Between PSP and Consumer Application.

Shared Token Transactions

The ability to transfer this data is known as a Shared Token Transaction. It lets you use tokens created in another system (such as a third-party shopping cart or a previous payment service provider) with BlueSnap and SAP DPA.

Common scenarios include:

Migrating vaulted shoppers when switching providers.
Capturing or refunding an authorization that started outside SAP.

Token-Based Transaction Endpoints

The following endpoints are specific to tokenized flows.

Action	Endpoint	Description
Get Card Token	`/core/v1/tokens/getforpaymentcard`	SAP checks a vaulted shopper's payment card information in BlueSnap.
Authorize	`/core/v1/tokens/getforauthorization`	SAP checks authorization for an external payment in BlueSnap.
Capture	`/core/v1/tokens/getfordirectcapture`	SAP checks direct capture for an external payment in BlueSnap.

Get Card Token

When calling /core/v1/tokens/getforpaymentcard, you must provide a PaymentCards object with the following parameters. For comprehensive details about this endpoint, refer to the SAP API reference:

Parameters	Values
`PaymentServiceProvider`	Four-character code provided by SAP DPA for BlueSnap. For example: `BSNP`
`PaytCardByPaytServiceProvider`	Payment card token from BlueSnap. For example: `tok4711`

The response will return a Digital Payment Add-on Payment Card Token (PaytCardByDigitalPaymentSrvc).

Authorize

When calling /core/v1/tokens/getforauthorization, you must provide an Authorizations object with the following parameters. For comprehensive details about this endpoint, refer to the SAP API reference:

Parameters	Values
`AuthorizationByPaytSrvcPrvdr`	The transaction ID provided by BlueSnap. For example: `38488222`
`PaymentServiceProvider`	Four-character code provided by SAP DPA for BlueSnap. For example: `BSNP`
`MerchantAccount`	BlueSnap merchant ID. For example: `2138589`
`DigitalPaymentAuthorizationType`	Identifier indicating the type of authorization performed. For example: `DPC2`
`AuthorizedAmountInAuthznCrcy`	The amount authorized at BlueSnap. For example: `35.62`
`AuthorizationCurrency`	Currency code (ISO 4217). For example: `USD`

The response will return the Digital Payment Add-on Payment Token (PaymentByDigitalPaymentService) that you can use to refund the payment.

Capture

When calling /core/v1/tokens/getfordirectcapture, you must provide a DirectCaptures object with the following parameters. For comprehensive details about this endpoint, refer to the SAP API reference:

Parameters	Values
`PaymentByPaymentServicePrvdr`	The ID of the transaction provided by BlueSnap. For example: `38488220`
`PaymentServiceProvider`	Four-character code provided by SAP DPA. For example: `BSNP`
`MerchantAccount`	BlueSnap merchant ID. For example: `2138589`
`DigitalPaymentDirectCaptureType`	Identifier indicating the type of direct capture performed. For example: `DPC2`
`AmountInPaymentCurrency`	The amount of the direct capture. Must match the amount authorized. For example: `35.62`
`PaymentCurrency`	Currency code (ISO 4217). For example: `USD`

The response will return the Digital Payment Add-on Payment Token (PaymentByDigitalPaymentService) that you can use to refund the payment.