Skip to main content

Support Sandbox Signup

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.

Direct API Implementation
SDK Version 2.0 Implementation
SDK Version 3.0 Implementation
Use Cases
Testing
Reference

Cybersource
Visa Acceptance
ANET Plus
Barclays
Bank of America
Cliq
National Australia Bank
Payzli

SDK Version 3.0 Implementation

Refer to these resources for information about implementing the Version 3.0 Payer Authentication SDK:

Android

Version 3.0 Android Integration Guide for Payer Authentication
Release History for Android

iOS

Version 3.0 iOS Integration for Payer Authentication
Release History for iOS

SDK Version 2.0 Implementation — The current mobile SDK implementation.

Was this page helpful?

Thanks for your feedback!

Want to share more details? Optional

Last published: September 29, 2026

On this page

Android
iOS

Loading…

POST

/pts/v2/payments

Authentication

Sandbox

Organization ID

Key ID

Secret Key

P12 file

Passphrase

Or paste PEM instead

Private key

Certificate

MLE cert

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

MLE Configuration

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

Request encryption — encrypt the request body to CyberSource's public cert. Needs an MLE cert (extracted from your .p12, or pasted). Response encryption — ask the server to encrypt the response to your key, then decrypt it here.

Response Key ID

Decryption .p12

Passphrase

Decryption 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

Language

Sending request…

Request history

MethodRequestStatusWhen

PAIGE

|

|

Checking browser compatibility…

0%

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%

©Copyright 1996 - 2026. All Rights Reserved.

Privacy
Terms of Use
Cookie Preferences