Recurring Payments (Early Access Beta)

Overview

Recurring payments allow merchants to offer subscription-based services and automate billing cycles. With CrissCross, merchants can securely store customer payment tokens and initiate recurring charges without requiring customer re-entry of payment details.

Tokenization for Recurring Payments

• Tokenization: The platform converts sensitive payment details into secure tokens. These tokens represent payment instruments such as cards or bank accounts.
• Reusable Tokens: Stored tokens enable merchants to charge customers repeatedly without needing to collect payment data again.

Example of Tokenized Payment Response:

1
{
2
  "id": "recurring_token_12345",
3
  "type": "card",
4
  "last_used": "2024-10-17T12:05:00Z",
5
  "card_details": {
6
    "brand": "Visa",
7
    "last4": "4242",
8
    "expiry_month": "12",
9
    "expiry_year": "2026"
10
  }
11
}

How It Works

1. Create Initial Payment:

   • Collect payment details from the customer during the first transaction.
   • The platform returns a payment token upon successful authorization.

2. Store Token:

   • Store the token securely within your merchant system for future transactions.

3. Initiate Recurring Charges:

   • Use the stored token to initiate future charges.
   • Optional: Allow customers to manage their payment methods via your portal.

How to create charges (API shape)

Recurring charges reuse the standard Collect payment flow:

• Create a checkout session: POST /v1/checkout/session
• Initiate the transaction: POST /v1/payment
• Verify status: GET /v1/payment/{transactionId}
• If additional authorization is required, use POST /v1/payment/authorize based on the returned authState

In Early Access, CrissCross can enable token-based recurring flows for eligible payment methods so you don’t need to re-collect raw payment details each cycle.

Best Practices

• Subscription Management: Merchants should handle subscription status changes (e.g., cancellations or reactivations) within their own systems.
• Expiry Handling: Monitor token expiry dates and notify customers in advance if updates are needed.
• Secure Storage: Store tokens in compliance with PCI standards to minimize risk.

Error Handling and Retries

The platform will automatically retry failed recurring payments based on configured rules. Merchants are notified via webhooks in case of repeated failures.