Skip to content
Last updated

Cards

Accept supported credit and debit card payments across online and in-person payment experiences.

Card capabilities vary based on the payment experience, transaction type, merchant configuration, and card network.

Deluxe supports card payment processing across supported card networks and payment channels.


Supported Card Networks

Card NetworkSupported
VisaYes
MastercardYes
American ExpressYes
DiscoverYes

Credit and Debit Card Support

Card TypeSupportedConsiderations
CreditYesStandard card processing supported.
Signature DebitYesSurcharge restrictions apply.
PIN DebitYes (Card Present Only)Surcharge restrictions apply.
PrepaidYesProcessing supported. Surcharge restrictions apply.
Commercial / Business CardsYesLevel 2 and Level 3 data supported through Payments API, Subscriptions, and Payment Links.
WEX FleetContact DeluxeAvailability varies by configuration.
Voyager FleetContact DeluxeAvailability varies by configuration.

Domestic vs International Cards

TypeSupported
DomesticYes
InternationalNo

Where Cards Can Be Used

ProductCard Support
Payments APIYes
Embedded Payments SDKYes
Hosted Payment Form (HPF)Yes
Vault / Stored Payment MethodsYes
WalletsYes
EMV Card Present APIsYes
Devices / TerminalsYes

Cards may be processed using:

  • Raw card data
  • Token
  • Vault ID (paymentMethodId)
  • Cryptogram
  • Network wallet credential
  • EMV terminal workflow

Supported Card Capabilities

CapabilityCard Support
Create / PurchaseYes
Authorization OnlyYes
Partial AuthorizationYes
Complete / CaptureYes
Void / CancelYes
RefundYes
Partial RefundYes
Multiple Partial RefundsYes
Card on FileYes
Tokenized PaymentsYes
Vaulted PaymentsYes
Recurring PaymentsYes
Mobile Wallet Funding SourcesYes
Incremental AuthorizationNo
Multiple CapturesNo
Authorization ExtensionNo

Merchant Requirements

Before accepting card payments, merchants must have:

  • Active Deluxe merchant account
  • Access token (partnerToken)
  • Client ID and Client Secret used to generate OAuth bearer tokens
  • Appropriate card payment enablement
  • Developer Portal access
  • Payments API access

Additional Requirements

Embedded and wallet implementations additionally require:

  • Secret key
  • JWT generation capability (HS256)

Optional Configuration

Depending on your implementation, additional configuration may be required.

FeatureAdditional Setup
Card VaultingVault enabled
TokenizationTokenization enabled
Apple PayMerchant linking and domain verification
Google PayMerchant linking
SurchargingMerchant-level enablement
Wallet AcceptanceWallet enablement

How Card Payments Work

Card payments follow a standard payment lifecycle.

Card payment workflow showing a payment request moving from the cardholder through the merchant, Deluxe Payments Platform, processor, card network, and issuing bank, followed by the payment response returning to the cardholder. Detailed workflow follows.

The card payment workflow shows how a payment request moves from the cardholder through the merchant, Deluxe Payments Platform, processor, card network, and issuing bank. The payment decision then follows the same path in reverse until the result is shown to the cardholder.

  1. 1

    Enter Card Details
    The cardholder enters card details on the merchant website or application.

  2. 2

    Submit Payment
    The merchant submits the payment to the Deluxe Payments Platform.

  3. 3

    Send Payment Processing Request
    The Deluxe Payments Platform sends the payment processing request to the processor.

  4. 4

    Route Transaction
    The processor routes the transaction to the card network.

  5. 5

    Request Approval
    The card network sends the approval request to the issuing bank.

  6. 6

    Approve or Decline Payment
    The issuing bank makes the final approval decision and returns the approve or decline result to the card network.

  7. 7

    Return Payment Decision
    The card network returns the payment decision to the processor.

  8. 8

    Return Response
    The processor returns the payment response to the Deluxe Payments Platform.

  9. 9

    Return Payment Status
    The Deluxe Payments Platform returns the payment status to the merchant.

  10. 10

    Show Result to Cardholder
    The merchant website or application displays the payment result to the cardholder.

The issuing bank ultimately approves or declines the transaction and places a hold on available funds during authorization.

Funds remain reserved until the payment is captured or the authorization expires.

Explore Transaction Types →


Card Verification & Security

Address Verification Service (AVS)

AVS helps verify a cardholder's billing address by comparing the street address and ZIP/postal code submitted with a card transaction against the information on file with the card issuer. Include the cardholder's billing address and zip code when submitting an eligible transaction, then evaluate the AVS response to determine whether the information matches. Use the result alongside other fraud prevention measures to decide whether to accept, review, or decline the transactions based on your business rules.

When AVS Runs

AVS is performed automatically during:

  • Create / Purchase
  • Authorize
Minimum Requirements
  • Must include billing street address and zip code to get an AVS response

Standalone AVS Check is available through the AVS API endpoint:


Card Verification Value (CVV)

CVV helps verify that a customer has access to the payment card by validating the security code provided during a transaction. Include the cardholder's CVV when submitting an eligible card transaction, then evaluate the CVV response to determine whether the code matches the card issuer's records. Use the result alongside other fraud prevention measures to determine whether to accept, review, or decline the transaction, and never store the CVV after authorization.

For supported card-not-present transactions, CVV validation confirms that the verification code provided by the customer matches the value on file with the issuer.

Best Practices

CVV should:

  • Be collected during payment
  • Be submitted for verification
  • Never be stored

Vaulting preserves:

  • Card PAN reference
  • Card reference information
  • Card expiration date

Vaulting never stores CVV data.

For CVV Response Codes, See Error Handling →


EMV

EMV is supported for card-present payment experiences.

Supported capabilities include:

  • EMV chip processing
  • EMV authorization data
  • EMV transaction certificates
  • Terminal device integrations

EMV functionality is available through dedicated EMV APIs and supported terminal workflows. Explore EMV API →