One-Click Payments

One-Click Payments streamline checkout for returning customers by eliminating the need to re-enter payment details. When enabled, customer information is securely stored during their first purchase. Subsequent transactions require minimal input—just CVV verification for credit cards or no interaction at all for PayPal one-time purchases. This simplified process leads to faster checkouts, improved conversion rates, and reduced declines from expired cards.

Available for: Credit Card, PayPal, SEPA, and all currencies.

  • One-Click Payments do not work with direct debit or crypto.

  • If Inquiry and Enable/Disable postbacks are set up, they will work as long as a username and password are sent with the transaction.

How One-Click Handles Different Purchase Types

One-Click payment processing varies depending on whether the transaction is a one-time purchase or a recurring subscription. The table below explains how purchaseIDs are managed in each scenario and how these transactions appear in your reporting systems.

Purchase Type How it Works with One-Click
One-Time Purchase
(example: digital downloads)		 The new payment is associated with the original purchaseID. In reports and postbacks, the One-Click is shown as a rebill to associate it with the original purchaseID.
Recurring Purchase
(example: a subscription)		 A new purchaseID is generated. In reports and postbacks, the One Click is shown as an Initial purchase to better track the membership lifecycle. Example: tracking a trial to full membership.

Getting Started

1. Prerequisites

Requirement Details
Segpay Merchant Account You must have an active Segpay merchant account.
Enabled Price Point The target price point must have one-click enabled.
OCToken Save the PurchaseID returned on the original sale to pass later as OCToken for hosted pay page or PurchaseId for the Web Service API.
API Credentials (SRS) Needed only when using the Web Service API implementation.

2. Enable One-Click for a Price Point

To offer One-Click payments to your consumers, you must enable One-Click for your target Price Point:

  1. Log into the Merchant Portal: https://mp.segpay.com/

  2. Navigate to My Websites > Price Points

  3. Edit or Add a new Price Point, check One Click Enabled, and Save.

3. Choose an Implementation Method

Method When to Choose Key Benefit
Hosted Pay Page Need 3DS, want Segpay to handle UI/security, low-code, strong compliance. Security, compliance, 3DS, easy integration.
Web Service API Need full control, embedded UX, automation, no 3DS, advanced developer resources. Flexibility, automation, custom experience.

Hosted Pay Page Implementation

When using this implementation method, Segpay hosts the payment page interface.

If a card has expired or is within three months of expiry, the payment page automatically shows the Expiration Date and CVV fields so customers can update details in one step (see image below).

Steps

  1. Construct Base URL:

    Base URL
    https://secure2.segpay.com/billing/OneClick.aspx?x-eticketid={EticketId}

  2. Append Mandatory Parameter:

    OCToken Parameter
    &OCToken={PurchaseID}

  3. Add Optional Parameters:

    See Segpay Processing API Guide for all the available parameters.

https://secure2.segpay.com/billing/OneClick.aspx?x-eticketid=122903:9689&OCToken=11223344

One-click Payment Result

With One-Click enabled, returning customers only need to provide the card's CVV, as illustrated below:

Web Service API Implementation

When using this implementation method, merchants call the One-Click Web Service API from their site or app.

  • The API attempts an automatic expiration-date extension for outdated cards, preventing avoidable declines.

  • No redirect is required; the transaction happens in the background

Authentication

The One-Click Web Service API uses HTTP Basic base64-encoded authentication. You'll need your SRS User ID and User Access Key (contact techsupport@segpay.com).

Authentication Header Format:

Authorization: Basic <UserID>:<Password>

Endpoint

POST https://srs.segpay.com/MerchantServices/one-click-tokens

Request Headers

Header Value
Content-Type application/json, application/xml, or application/x-www-form-urlencoded
Accept application/json or application/xml

Request Parameters

Parameter Type Required Description Example
EticketID String Yes A package:pricepoint identifier string passed via the x-eticketid parameter. When used, individual PackageId and PricePointId parameters cannot be included. 12345:67890
PackageID Number Yes A package identifier parameter that is only allowed when the EticketId parameter is not used. 12345
PricePointID Number Yes A price point identifier parameter that is only allowed when the EticketId parameter is not used. 67890
PurchaseID Number Yes A purchase identifier that must be passed via the "OcToken" parameter.  

Example Requests

JSON

 

If the transaction is declined, you'll see a decline code and reason: IE 05:Do Not Honor: COF Expiration Date is Expired. In this case, merchants should redirect consumers to their One-Click hosted pay page using their regular one-click payment link.