website logo
⌘K
πŸš€Getting Started
Welcome Developers
Web integration Architecture
Integration Prerequisite
πŸ”Authentication
πŸ“ŒSandbox and Live Environment
πŸ› οΈIntegration Options
POS Integration Guide
Direct API integration Guide
βš™οΈPlugins
πŸ‡²πŸ‡ΎMalaysia
πŸ‡ΈπŸ‡¬Singapore
πŸ›οΈMarketing brand guide
πŸ”Logo introduction
πŸ–₯️Sitewide
πŸ‘—Product & service pages
πŸ‘œCheckout and cart page
🌐Website Assets
API REFERENCE
Docs powered byΒ archbeeΒ 
4min

Checkout Object

This step is done internally by the octifi-websdk.js

Are you using octifi-websdk.js?

If you are using octifi-websdk.js you can safely skip this page.

What is a checkout object?

Once the customer decides to pay with octifi, the hosted-checkout (octifi-websdk.js) calls the backend to create a checkout object and return a checkout_token to the merchant via callback.

Checkout Api returns a checkout_token

  • /checkout/create: For details see checkout apis in the Api referenceο»Ώ
  • This api uses a Public API key and normally used in the frontend.
  • Authorization: Api-Key public_api_key
  • Checkout only authorise the payment

What is the difference between checkout and charge?

In a nutshell:

  1. Customer Checkout is step 1
  2. Charge/create is the step 2
  3. Charge/capture is step 3

Notes:

  • Charge api takes checkout_token as a parameter
  • Charge capture api should be called from the backend (server side) and requires a private key.
  • More details about charge are here: https://docs.octifi.com/chargesο»Ώ
  • Api: /charge/create/{checkout_token}/
    • For details see charge apis in the Api referenceο»Ώ

ο»Ώ

Updated 03 Mar 2023
Did this page help you?
Yes
No
UP NEXT
Charges
Docs powered byΒ archbeeΒ 
TABLE OF CONTENTS
Are you using octifi-websdk.js?
What is a checkout object?
What is the difference between checkout and charge?