Open the command palette and create a Go project directory with the following files:
- main.go
- app.html
- go.mod files.
Steps to integrate Curlec Payment Gateway with Go SDK.
Follow the steps given below to integrate Curlec Payment Gateway with your Go website.
File Name | Purpose |
---|---|
main.go | The main Go file where Orders API is integrated. |
app.html | Contains a form where the customers fills their details. Once the customer submits the form, the Orders API is fired and an order_id is generated. |
go.mod | The .mod file defines the module path. |
To integrate Curlec Payment Gateway on your Go website:
1.1
.1.2
.1.3
.1.4
.1.5
.1.6
.1.7
.Open the command palette and create a Go project directory with the following files:
Order is an important step in the payment process.
order_id
received in the response should be passed to the checkout. This ties the Order with the payment and secures the request from being tampered.Handy Tips
You can capture payments automatically with one-time
on the Curlec Dashboard.Create a file, for example, main.go
and add the API code given below:
Here is the list of parameters for creating the order:
amount
mandatory
integer
The transaction amount is expressed in the currency's subunit. For example, for an actual amount of RM 299.35, the value of this field should be 29935
.
currency
mandatory
string
The currency in which the transaction should be made. Length of the currency must be 3 characters.
receipt
optional
string
Pass the receipt id created for this order. Maximum length is 40 characters.
notes
optional
json object
Optional notes for order. Key-value pair used to store additional information about the entity. Maximum 15 key-value pairs, 256 characters (maximum) each. For example, "note_key": "Beam me up Scotty”
.
partial_payment
optional
boolean
Indicates whether the customer can make a partial payment. Possible values:
true
: Yes, the customer can make partial payments.false
(default): No, the customer cannot make partial payments.When the order is created successfully, an order_id
is returned in the response. You need to store it against the order defined in your system.
Know more about
.Descriptions for the response parameters are present in the
parameters table.The error response parameters are available in the
.Add the Curlec Checkout options in your project. For example, if you are using HTML for your frontend, create a page called app.html and add the Pay button on your web page using the checkout code and either the:
Callback URL | Handler Function |
---|---|
When you use this:
| When you use this:
|
Handy Tips
For FPX payments, you must use the Callback URL sample code for checkout. You should send the following parameters along with the other checkout parameters:
callback_url
with the URL to which customers should be redirected after payment completion.redirect
with the value as true
.Copy-paste the parameters as options
in your code:
key
mandatory
string
API Key ID generated from the Curlec Dashboard.
amount
mandatory
integer
The amount to be paid by the customer in currency subunits. For example, if the amount is RM 500.00, enter 50000
.
currency
mandatory
string
The currency in which the payment should be made by the customer.
name
mandatory
string
The business name shown on the Checkout form. For example, Acme Corp.
description
optional
string
Description of the purchase item shown on the Checkout form. It should start with an alphanumeric character.
image
optional
string
Link to an image (usually your business logo) shown on the Checkout form. Can also be a base64 string if you are not loading the image from a network.
order_id
mandatory
string
Order ID generated via
prefill
object
You can prefill the following details at Checkout.
Boost Conversions and Minimise Drop-offs
contact
parameter of the JSON request's prefill
object. Format: +(country code)(phone number). Example: “contact": "+919000090000").name
optional
string
Cardholder's name to be pre-filled if customer is to make card payments on Checkout. For example, Siti Aisyah.
optional
string
Email address of the customer.
contact
optional
string
Phone number of the customer. The expected format of the phone number is + {country code}{phone number}
. If the country code is not specified, 60
will be used as the default value. This is particularly important while prefilling contact
of customers with phone numbers issued outside Malaysia. Examples:
+60
is added to it as +601113455567.method
optional
string
Pre-selection of the payment method for the customer. Will only work if contact
and email
are also pre-filled.
Possible value is card
.
notes
optional
object
Set of key-value pairs that can be used to store additional information about the payment. It can hold a maximum of 15 key-value pairs, each 256 characters long (maximum).
theme
object
Thematic options to modify the appearance of Checkout.
hide_topbar
optional
boolean
Used to display or hide the top bar on the Checkout form. This bar shows the selected payment method, phone number and gives the customer the option to navigate back to the start of the Checkout form. Possible values:
true
: Hides the top barfalse
(default): Displays the top bar.color
optional
string
Enter your brand colour's HEX code to alter the text, payment method icons and CTA (call-to-action) button colour of the Checkout form.
backdrop_color
optional
string
Enter a HEX code to change the Checkout's backdrop colour.
modal
object
Options to handle the Checkout modal.
backdropclose
optional
boolean
Indicates whether clicking the translucent blank space outside the Checkout form should close the form. Possible values:
true
: Closes the form when your customer clicks outside the checkout form.false
(default): Does not close the form when customer clicks outside the checkout form.escape
optional
boolean
Indicates whether pressing the escape key should close the Checkout form. Possible values:
true
(default): Closes the form when the customer presses the escape key.false
: Does not close the form when the customer presses the escape key.handleback
optional
boolean
Determines whether Checkout must behave similar to the browser when back button is pressed. Possible values:
true
(default): Checkout behaves similarly to the browser. That is, when the browser's back button is pressed, the Checkout also simulates a back press. This happens as long as the Checkout modal is open.false
: Checkout does not simulate a back press when browser's back button is pressed.confirm_close
optional
boolean
Determines whether a confirmation dialog box should be shown if customers attempts to close Checkout. Possible values:
true
: Confirmation dialog box is shown.false
(default): Confirmation dialog box is not shown.ondismiss
optional
function
Used to track the status of Checkout. You can pass a modal object with ondismiss: function()\{\}
as options. This function is called when the modal is closed by the user.
animation
optional
boolean
Shows an animation before loading of Checkout. Possible values:
true
(default): Animation appears.false
: Animation does not appear.callback_url
optional
string
Customers will be redirected to this URL on successful payment. Ensure that the domain of the Callback URL is allowlisted. This parameter is mandatory for FPX payments.
redirect
optional
boolean
Determines whether to post a response to the event handler post payment completion or redirect to Callback URL. callback_url
and redirect
parameters are mandatory for FPX payments. Possible values:
true
: Customer is redirected to the specified callback URL in case of payment failure. For FPX payments, the redirect
parameter should always be sent as true
.false
(default): Customer is shown the Checkout popup to retry the payment.customer_id
optional
string
Unique identifier of customer.
remember_customer
optional
boolean
Determines whether to allow saving of cards. Can also be configured via the
true
: Enables card saving feature.false
(default): Disables card saving feature.timeout
optional
integer
Sets a timeout on Checkout, in seconds. After the specified time limit, the customer will not be able to use Checkout.
readonly
object
Marks fields as read-only.
contact
optional
boolean
Used to set the contact
field as readonly. Possible values:
true
: Customer will not be able to edit this field.false
(default): Customer will be able to edit this field.optional
boolean
Used to set the email
field as readonly. Possible values:
true
: Customer will not be able to edit this field.false
(default): Customer will be able to edit this field.name
optional
boolean
Used to set the name
field as readonly. Possible values:
true
: Customer will not be able to edit this field.false
(default): Customer will be able to edit this field.hidden
object
Hides the contact details.
contact
optional
boolean
Used to set the contact
field as optional. Possible values:
true
: Customer will not be able to view this field.false
(default): Customer will be able to view this field.optional
boolean
Used to set the email
field as optional. Possible values:
true
: Customer will not be able to view this field.false
(default): Customer will be able to view this field.allow_rotation
optional
boolean
Used to rotate payment page as per screen orientation. Applicable from Android SDK version 1.6.4 and above. Possible values:
true
: Payment page can be rotated.false
(default): Payment page cannot be rotated.retry
optional
object
Parameters that enable retry of payment on the checkout.
enabled
boolean
Determines whether the customers can retry payments on the checkout. Possible values:
true
(default): Enables customers to retry payments.false
: Disables customers from retrying the payment.max_count
integer
The number of times the customer can retry the payment. We recommend you to set this to 4. Having a larger number here can cause loops to occur.
Watch Out!
Web Integration does not support the max_count
parameter. It is applicable only in Android and iOS SDKs.
config
optional
object
Parameters that enable configuration of checkout display language.
display
object
Child parameter that enables configuration of checkout display language.
language
string
The language in which checkout should be displayed. Possible value is en
: English.
Handy Tips
The open method of the Razorpay object (rzp1.open()
) must be invoked by your site's JavaScript, which may or may not be a user-driven action such as a click.
Multiple payment methods are available on Curlec Standard Checkout.
The way the Payment Success and Failure scenarios are handled depends on the
you used in the last step.If you used the sample code with the callback URL:
razorpay_payment_id
, razorpay_order_id
and razorpay_signature
in the response object of the successful payment. Only successful authorisations are auto-submitted.If you used the sample code with the handler function:
razorpay_payment_id
, razorpay_order_id
and razorpay_signature
). Collect these and send them to your server.Enter go mod tidy
in the command palette and run the command.
This builds the go.mod
file and imports the
A successful payment returns the following fields to the Checkout form.
razorpay_payment_id
string
Unique identifier for the payment returned by Checkout only for successful payments.
razorpay_order_id
string
Unique identifier for the order returned by Checkout.
razorpay_signature
string
Signature returned by the Checkout. This is used to verify the payment.
This is a mandatory step that allows you to confirm the authenticity of the details returned to the checkout for successful payments.
To verify the razorpay_signature
returned to you by the checkout:
Create a signature in your server using the following attributes:
Attribute | Description |
---|---|
order_id | Retrieve the order_id from your server. Do not use the razorpay_order_id returned by checkout. |
razorpay_payment_id | Returned during checkout. |
key_secret | Available in your server. The key_secret that was generated from the . |
Use the SHA256 algorithm, the razorpay_payment_id
and the order_id
to construct a HMAC hex digest as shown below:
generated_signature = hmac_sha256(order_id + "|" + razorpay_payment_id, secret);if (generated_signature == razorpay_signature) {payment is successful}
If the signature you generate on your server matches the razorpay_signature
returned to you by the checkout, the payment received is from an authentic source.
Use the code given below to generate signature on your server:
import ( razorpay "github.com/razorpay/razorpay-go" )client := razorpay.NewClient("YOUR_KEY_ID", "YOUR_SECRET")params := map[string]interface{}{"razorpay_order_id": "order_IEIaMR65cu6nz3","razorpay_payment_id": "pay_IH4NVgf4Dreq1l",}signature := "0d4e745a1838664ad6c9c9902212a32d627d68e917290b0ad5f08ff4561bc50f";secret := "EnLs21M47BllR3X8PSFtjtbd";utils.VerifyPaymentSignature(params, signature, secret)
You can track the payment status in three ways:
Handy Tips
captured
. Refer to the payment capture settings page to know how to .To verify the payment status from the Dashboard:
You can use Curlec webhooks to configure and receive notifications when a specific event occurs. When one of these events is triggered, we send an HTTP POST payload in JSON to the webhook's configured URL. Know how to
If you have subscribed to the order.paid
webhook event, you will receive a notification every time a customer pays you for an order.
Is this integration guide useful?
ON THIS PAGE