Welcome to the preview portal — This is an early release of the new Doc Hub experience, with more content coming soon.

GET STARTED
ACCEPT PAYMENTS
PAYMENT METHODS
- Buy Now Pay Later
- Digital Wallets
- Local Payments
- Pay by Bank
CHECKOUT EXPERIENCE
TOKENIZATION
PAYER AUTHENTICATION
BILLING & SUBSCRIPTIONS
POST-TRANSACTION PROCESSING
INDUSTRY
DEVELOPER TOOLS

No results.

Cybersource
Visa Acceptance
Barclays
Bank of America
Cliq
National Australia Bank

Payments with Payment Instrument Tokens

This page describes payment operations using payment instrument tokens. You can authorize payments and make credits using payment instrument tokens that you have created.

Manage Payment Instrument Tokens
Endpoints

Was this page helpful?

Thanks for your feedback!

Want to share more details? Optional

Last published: October 28, 2026

Not available for your audience

This page isn't available for your current audience selection.

On this page

Loading…

POST

/pts/v2/payments

Authentication

Sandbox

Organization ID

Key ID

Secret Key

P12 file

Passphrase

Algorithm

Or paste PEM instead

Private key

Certificate

MLE cert

Enter Organization ID, Key ID, and Secret Key to send.

MLE Configuration

Choose a JWT authentication type (in the Authentication section) to enable Message-Level Encryption.

Request encryption — encrypt the request body to CyberSource's public (SJC) cert. Taken from your Certificate .p12, your Response MLE .p12 below, or pasted here.

MLE cert

Response encryption — ask the server to encrypt the response to your key, then decrypt it here.

Response Key ID

Response MLE .p12

Passphrase

Your REST – API Response MLE key: it decrypts responses and carries the SJC cert for request encryption. Everything runs in your browser — the .p12 is never uploaded or stored. Only .p12 files are accepted.

URL Parameters

Query Parameters

Headers

Sample Library

Payment Processor Type

Scenario Type

Sample Request

Body

MLE Encrypted request — sent as the encryptedRequest field

⇄

Sending request…

Request history

MethodRequestStatusWhen

PAIGE

Checking browser compatibility…

Slow mode — running on CPU. Responses take 45–105s and may be less accurate. For full speed, use Chrome or Edge with WebGPU enabled.

⚡ Common questions are instant — warming up the full assistant 0%

DOCS

Privacy
Terms of Use
Cookie Preferences