---
schema_version: "1"
id: da385a777a98e8908a63e4094fa9ba64505f2d4d13e38619cb384379f05773db
title: Use Cases for the CommercePayments Namespace
collection: legacydeveloper
version: current
locale: en-us
portal_url: https://docs.salesforce.com/legacydeveloper/current/en-us/apexcode/apex_commercepayments_use_cases.md
canonical_url: https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_commercepayments_use_cases.htm
source_site: developer.salesforce.com
content_type: documentation
content_hash: 08b5254a7d7e99b5882069df7e9f380a572449d7eb97a24cb8c711c1a7dd3a99
description: Review walkthroughs, use cases, and reference material for the CommercePayments platform.
---
# Use Cases for the CommercePayments Namespace

Review walkthroughs, use cases, and reference material for the CommercePayments platform.

To review CommercePayments class reference docs, go to [CommercePayments Namespace](https://developer.salesforce.com/docs/atlas.en-us.264.0.apexref.meta/apexref/apex_namespace_commercepayments.htm).

- **[Payment Gateway Adapters](https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_commercepayments_adapter_intro.htm)**  
    Payment gateway adapters represent the bridge between your payments platform in Salesforce and an external payment gateway.
- **[Payment Authorization Reversal Service](https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_commercepayments_rev_service_intro.htm)**  
    An authorization reversal is a transaction that negates an authorization by releasing the hold on funds in a customer’s payment method.
- **[Tokenization Service](https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_commercepayments_tokenization_service_intro.htm)**  
    The credit card tokenization process replaces sensitive customer information with a one-time algorithmically generated number, called a token, used during the payment transaction. Salesforce stores the token and then uses that token as a representation of the credit card used for transactions. The token lets you store information about the credit card without storing sensitive customer data, such as credit card numbers, in Salesforce.
- **[Alternative Payment Methods](https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_commercepayments_alt_payment_methods.htm)**  
    An alternative payment method allows customers to store and represent payment method information not represented by another pre-defined payment method such as CardPaymentMethod or DigitalWallet. Common examples of alternative payment methods include CashOnDeliver, Klarna, and Direct Debit. Alternative payment methods are available in API v51.0 and later.
- **[Process Payments](https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_commercepayments_process_payments.htm)**  
    Process a payment in the payment gateway.
- **[Process Refund](https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_commercepayments_process_refund.htm)**  
    Process a refund in the payment gateway.
- **[Idempotency Guidelines](https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_commercepayments_idempotency_guidelines.htm)**  
    An idempotent payment gateway recognizes duplicate requests, submitted in error or maliciously, and processes them without charging twice. When your gateway supports idempotency, check for duplicates in your adapter before you send a callout.
- **[Sample Payment Gateway Implementation for CommercePayments](https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_commercepayments_ref_github_repo.htm)**  
    We’ve created a GitHub repository containing code samples for a sample Payeezy payment gateway implementation with the CommercePayments namespace. Review the sample code if you need help with configuring your payment gateway implementation.