1. Non-3DS Payment
Sipay API Documentation
EN
  • EN
  • TR
  • Overview
    • Getting Started
    • Test Cards
    • IP Restriction
  • Authentication
    • Token Generation
      POST
  • Installments & Commission
    • Installment Details
      POST
    • Commission
      POST
    • Merchant Installments
      POST
  • HASH
    • Hash Creation
    • Hash Validation
  • Non-3DS Payment
    • Non-3DS Payment Flow
    • Non-3DS Card Payment
      POST
    • Non-3DS Recurring Payment
      POST
    • Non-3DS Insurance Payment
      POST
    • Non-3DS Pre-Authorization Payment
      POST
    • Confirm Payment
      POST
  • 3D Secure Payment
    • 3D Secure Payment Flow
    • 3D Secure Card Payment
      POST
    • 3D Secure Recurring Payment
      POST
    • 3D Secure Pre-Authorization Payment
      POST
    • Complete Payment
      POST
    • Confirm Payment
      POST
    • 3D Secure Agriculture Payment
      POST
  • Non-3DS and 3DS Payment with Sipay
    • Purchase Link Example
    • Non-3DS and 3D Secure Payment with Sipay
      POST
  • Check Status
    • Check Status
  • Payment with Saved Card
    • Card Registration
    • 3D Secure Pay by Card Token
    • Non-3DS Pay by Card Token
    • Retrieving Saved Card
    • Edit Saved Card
    • Delete Saved Card
  • Recurring
    • Recurring Query Search
    • Recurring Plan Process
    • Recurring Plan Update
  • Refund
    • Refund
  • Cashout
    • Cashout to Bank
  • Webhook
    • Webhook
  • Status Codes
    • Status Codes
  • Plugin
    • Magento v1
    • Magento v2
    • Opencart
    • Presta
    • Woocommerce
    • Shopify
  1. Non-3DS Payment

Non-3DS Payment Flow

Non-3DS Payment
A Non-3DS payment is a payment transaction in which the cardholder is not redirected to a 3D Secure authentication page. In this type of transaction, card details are transmitted through the payment system, and the transaction is finalized based on the card issuer’s authorization response. Since 3D Secure authentication is not requested from the user, the transaction can be completed without an additional authentication step.

The following endpoints are recommended for initial review.
To generate a token: token
To check installments: getpos


Hash must be generated for each request. Example hash algorithms are included within the payment request samples for each endpoint.

#

Hash Parameters#

The parameters and their order to be used for the hash algorithm are as follows:
total
installment
currency_code
merchant_key
invoice_id
app_secret
For more details : Hash Information
Previous
Non-3DS Payment
Next
Non-3DS Card Payment
Built with