The following scopes are available:<\/p>\n
- \n
- Viewing webhooks<\/a><\/li>\n
- Viewing and editing webhooks<\/a><\/li>\n
- Make online payments<\/a>\n
- \n
- Integrating online payments using OAuth<\/a>\n
- \n
- Step 1: Add allowed origins<\/a><\/li>\n
- Step 2: Generate a client key<\/a><\/li>\n
- Step 3: Retrieve your URL prefix<\/a><\/li>\n<\/ul><\/li>\n<\/ul><\/li>\n
- Tokenize payment details<\/a><\/li>\n
- Handle raw card data<\/a><\/li>\n
- Manage payment links<\/a><\/li>\n
- Modify account settings<\/a><\/li>\n<\/ul>\n
Viewing webhooks<\/h2>\n
Scope identifier<\/strong>:
psp.webhook:read<\/code><\/p>\nLets you view webhook configurations for your customer's merchant account.<\/p>\n
Gives access to the following Management API requests:<\/p>\n
- \n
- GET \/merchants\/{merchantId}\/webhooks<\/a><\/li>\n
- GET \/merchants\/{merchantId}\/webhooks\/{webhookId}<\/a><\/li>\n
- POST \/merchants\/{merchantId}\/webhooks\/{webhookId}\/test<\/a><\/li>\n<\/ul>\n
Viewing and editing webhooks<\/h2>\n
Scope identifier<\/strong>:
psp.webhook:write<\/code><\/p>\nLets you view, create, edit, and delete webhook configurations for your customer's merchant account.<\/p>\n
Gives access to the following Management API requests:<\/p>\n
- \n
- GET \/merchants\/{merchantId}\/webhooks<\/a><\/li>\n
- GET \/merchants\/{merchantId}\/webhooks\/{webhookId}<\/a><\/li>\n
- POST \/merchants\/{merchantId}\/webhooks\/{webhookId}\/test<\/a><\/li>\n
- POST \/merchants\/{merchantId}\/webhooks<\/a><\/li>\n
- PATCH \/merchants\/{merchantId}\/webhooks\/{webhookId}<\/a><\/li>\n
- DELETE \/merchants\/{merchantId}\/webhooks\/{webhookId}<\/a><\/li>\n<\/ul>\n
Make online payments<\/h2>\n
Scope identifier<\/strong>:
psp.onlinepayment:write<\/code><\/p>\nLets you process online payments on behalf of your customer.<\/p>\n
This scope does not let you:<\/p>\n
- \n
- Tokenize payment details<\/a><\/li>\n
- Handle raw card data<\/a><\/li>\n
- Manage payment links<\/a><\/li>\n<\/ul>\n
Request these scopes separately.<\/p>\n
Gives access to the following Management API requests:<\/p>\n
- \n
- POST \/me\/allowedOrigins<\/a><\/li>\n
- POST \/me\/generateClientKey<\/a>
\/me\/generateClientKey<\/code><\/li>\n<\/ul>\nGives access to the following Checkout API<\/a> request groups:<\/p>\n
- \n
- Payments<\/li>\n
- Modifications<\/li>\n
- Recurring (only GET \n
\/storedPaymentMethods<\/code>\n<\/a>). Requires Checkout v70.<\/li>\n- Orders<\/li>\n
- Utility<\/li>\n<\/ul>\n
Integrating online payments using OAuth<\/h3>\n
When integrating online payments using OAuth, remember that OAuth is simply an alternative method of authenticating API requests. This means all our online payments documentation<\/a> still applies.<\/p>\n
However, because OAuth doesn't grant you access to your customers' Customer Area, you can only set up the resources for client-side authentication through our APIs, outlined in the step below:<\/p>\n
Step 1: Add allowed origins<\/h4>\n
Allowed origins<\/a> are domains from which you make client-side requests. This means you need to add the domains on which you are accepting payments as allowed origins. To do so, make a POST request to the \n
\/me\/allowedOrigins<\/code>\n<\/a> endpoint.<\/p>\nStep 2: Generate a client key<\/h4>\n
When using Components or Drop-in to accept payments online, you need a client key for client-side authentication<\/a>.<\/p>\n
To generate your client key, make a POST request to the
\/me\/generateClientKey<\/code> endpoint:<\/p>\n
- POST \/me\/generateClientKey<\/a>
- Handle raw card data<\/a><\/li>\n
- GET \/merchants\/{merchantId}\/webhooks\/{webhookId}<\/a><\/li>\n
- GET \/merchants\/{merchantId}\/webhooks\/{webhookId}<\/a><\/li>\n
- Step 2: Generate a client key<\/a><\/li>\n
- Step 1: Add allowed origins<\/a><\/li>\n
- Viewing and editing webhooks<\/a><\/li>\n
![\"-white_check_mark-\"](\"\/user\/data\/smileys\/emoji\/white_check_mark.png\" "\\"-white_check_mark-\\"")
<\/td>\n