This is a Frappe-based application that integrates with the Tingg API from Cellulant, providing support for automatically receiving and reconciling payments within the system.
- Tingg Settings: Configure Live or Sandbox environments.
- Tingg Register URL: Allows configuration of
Callback URL
andCustomer URL
- Tingg Payment Register: Records incoming payment transactions received via the Callback URL.
This DocType allows setup of both live and sandbox environments. Additionally, on save, it creates a Mode of Payment
, Payment Gateway
and Payment Gateway Account
- Payment Gateway Name: Desired name for the the Payment Gateway.
- Sandbox: Tick if the settings are for the sandbox environment.
This DocType is responsible for the generation of the Callback URL and Customer URL which are shared with for configuration.
- Company: This is the company associated with the Tingg Register URL.
- Mode of Payment: Identifies the payment mode for better categorization in your accounting or ERP system.
- Callback URL: This is a URL used to receive successful payments remitted to your Tingg account into your ERP when a payment is made.
- Customer URL: This is a URL to query a customer's outstanding balance from your ERP.
This DocType is responsible for acknowledging and reconciling all payments made to your ERP system.
- Customer: Identity of the customer making the payment.
- Customer Name: Name of the customer.
- Company: Company against which the payment is made.
- Mode of Payment: Payment mode used to make the payment.
- Amount Paid: The total amount transacted.
- Currency: Currency used for the transaction.
- Service ID:
- Service Code:
- Client Code:
- Payer Narration: Information about the payment for instance amount paid and Till Number
- Receiver Narration: Provides information on whether the record has been auto acknowledged.
- Status Description: The response short description.
- Merchant Payment IDs:
- Beep Transaction ID: Cellulant's unqique identifier for the transaction being acknowledged.
- Payer Transaction ID: The unique identifier tied to the client.
- Payment Entry: This is a record in the ERP indicating that a payment has been made for an invoice
- Submit Payment: This is a boolean value that indicates whether to submit the payment or not.
- MSISDN: Customer's phone number.
- Hashed MSISDN: Hashed version of a customer's phone number.
- Account Number:
- Extra Data: Any extra data usually in JSON format.
- Ensure you have a working Frappe and ERPNext instance.
- Clone this repository into your Frappe bench apps directory.
bench get-app https://github.com/navariltd/Frappe-Tingg-Payments
- Install the app into your site using:
bench --site [sitename] install-app frappe_tingg_payments
-
Configure "Tingg Settings" and "Tingg Register URL" in the system.
-
Copy "Callback URL" and "Customer URL" to Cellulant for configuration.
agpl-3.0