Create an order using Orders API in server. This generates an order_id when the customer places an order on your app. This order_id must be passed during the checkout.
Watch Out!
Do not create the order on your client. Order must be created on the server only.
CopyRazorpayClient client = new RazorpayClient(your_key_id, your_secret);
Dictionary<string, object> options = new Dictionary<string,object>();
options.Add("amount", 50000); // amount in the smallest currency unit
options.add("receipt", "order_rcptid_11");
options.add("currency", "INR");
Order order = client.Order.Create(options);
Here is the list of parameters for creating an order:
amountmandatory
integer The transaction amount, expressed in the currency subunit, such as paise (in case of INR). For example, for an actual amount of ₹299.35, the value of this field should be 29935.
currencymandatory
string The currency in which the transaction should be made. See the list of supported currencies. Length must be of 3 characters.
receiptoptional
string Your receipt id for this order should be passed here. Maximum length 40 characters.
notesoptional
json object Key-value pair that can be 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_paymentoptional
boolean Indicates whether the customer can make a partial payment. Possible values:
true: The customer can make partial payments.
false (default): The customer cannot make partial payments.
first_payment_min_amountoptional
integer Minimum amount that must be paid by the customer as the first partial payment. For example, if an amount of ₹7,000 is to be received from the customer in two installments of #1 - ₹5,000, #2 - ₹2,000, then you can set this value as 500000. This parameter should be passed only if partial_payment is true.
To quickly load the Checkout form, the preload method of Checkout must be called much earlier than the other methods in the payment flow. The loading time of the preload resources can vary depending on your network's bandwidth.
CopyclassPaymentActivity: Activity(), PaymentResultListener {
val TAG:String = PaymentActivity::class.toString()
override fun onCreate(savedInstanceState: Bundle?) {
super.onCreate(savedInstanceState)
setContentView(R.layout.activity_payment)
/*
* To ensure faster loading of the Checkout form,
* call this method as early as possible in your checkout flow
* */
Checkout.preload(applicationContext)
var button: Button = findViewById(R.id.btn_pay)
button.setOnClickListener {
startPayment()
}
}
Create an instance of the Checkout and pass the payment details and options as a JSONObject. Ensure that you add the order_id generated in Step 3.
CopypublicvoidstartPayment() {
checkout.setKeyID("<YOUR_KEY_ID>");
/**
* Instantiate Checkout
*/Checkoutcheckout=newCheckout();
/**
* Set your logo here
*/
checkout.setImage(R.drawable.logo);
/**
* Reference to current activity
*/finalActivityactivity=this;
/**
* Pass your payment options to the Razorpay Checkout as a JSONObject
*/try {
JSONObjectoptions=newJSONObject();
options.put("name", "Merchant Name");
options.put("description", "Reference No. #123456");
options.put("image", "https://s3.amazonaws.com/rzp-mobile/images/rzp.png");
options.put("order_id", "order_DBJOWzybf0sJbb");//from response of step 3.
options.put("theme.color", "#3399cc");
options.put("currency", "INR");
options.put("amount", "50000");//pass amount in currency subunits
options.put("prefill.email", "gaurav.kumar@example.com");
options.put("prefill.contact","9988776655");
JSONObjectretryObj=newJSONObject();
retryObj.put("enabled", true);
retryObj.put("max_count", 4);
options.put("retry", retryObj);
checkout.open(activity, options);
} catch(Exception e) {
Log.e(TAG, "Error in starting Razorpay Checkout", e);
}
}
Copyprivate fun startPayment() {
/*
* You need to pass current activity in order to let Razorpay create CheckoutActivity
* */
val activity:Activity = thisvalco= Checkout()
try {
valoptions= JSONObject()
options.put("name","Razorpay Corp")
options.put("description","Demoing Charges")
//You can omit the image option to fetch the image from dashboard
options.put("image","https://s3.amazonaws.com/rzp-mobile/images/rzp.png")
options.put("theme.color", "#3399cc");
options.put("currency","INR");
options.put("order_id", "order_DBJOWzybf0sJbb");
options.put("amount","50000")//pass amount in currency subunitsvalretryObj=newJSONObject();
retryObj.put("enabled", true);
retryObj.put("max_count", 4);
options.put("retry", retryObj);
valprefill= JSONObject()
prefill.put("email","gaurav.kumar@example.com")
prefill.put("contact","9876543210")
options.put("prefill",prefill)
co.open(activity,options)
}catch (e: Exception){
Toast.makeText(activity,"Error in payment: "+ e.message,Toast.LENGTH_LONG).show()
e.printStackTrace()
}
}
Handy Tips
When you paste the checkout options given above, the following error message appears: 'TAG has private access in androidx.fragment.app.FragmentActivity'
You can resolve this by adding the following code:
Checkout.open() launches the Checkout form where the customer completes the payment and returns the payment result via appropriate callbacks on the PaymentResultListener.
Payment Options in JSONObject:
All available options in the Standard Web Checkout are also available in Android.
You must pass these parameters in the Checkout to initiate the payment.
keymandatory
string API Key ID generated from the Razorpay Dashboard.
amountmandatory
integer The amount to be paid by the customer in currency subunits. For example, if the amount is ₹100, enter 10000.
currencymandatory
string The currency in which the payment should be made by the customer. See the list of supported currencies.
namemandatory
string The business name shown on the Checkout form.
descriptionoptional
string Description of the purchase item shown on the Checkout form. Must start with an alphanumeric character.
imageoptional
string Link to an image (usually your business logo) shown on the Checkout form. Can also be a base64 string, if loading the image from a network is not desirable.
object You can prefill the following details at Checkout.
nameoptional
string Cardholder's name to be pre-filled if customer is to make card payments on Checkout.
emailoptional
string Email address of the customer.
contactoptional
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, 91 will be used as the default value. This is particularly important while prefilling contact of customers with phone numbers issued outside India. Examples:
+14155552671 (a valid non-Indian number)
+919977665544 (a valid Indian number). If 9977665544 is entered, +91 is added to it as +919977665544.
methodoptional
string Pre-selection of the payment method for the customer. Will only work if contact and email are also pre-filled. Possible values
card
netbanking
wallet
emi
upi
notesoptional
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_topbaroptional
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 are:
true: Hides the top bar
false (default): Displays the top bar.
coloroptional
string Enter your brand colour's HEX code to alter the appearance of Checkout form.
backdrop_coloroptional
string Enter a HEX code to change the Checkout's backdrop colour.
modal
object Options to handle the Checkout modal.
backdropcloseoptional
boolean Indicates whether clicking the translucent blank space outside the Checkout form should close the form. Possible values are:
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.
escapeoptional
boolean Indicates whether pressing the escape key should close the Checkout form. Possible values are:
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.
handlebackoptional
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_closeoptional
boolean Determines whether a confirmation dialog box should be shown when customers attempt to close Checkout. Possible values:
true: Confirmation dialog box is shown.
false (default): Confirmation dialog box is not shown.
ondismissoptional
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.
animationoptional
boolean Show an animation before loading of Checkout.
true(default): Animation appears.
false: Animation does not appear.
subscription_idoptional
string If you are accepting recurring payments using Razorpay Checkout, you should pass the relevant subscription_id to the Checkout. Know more about Subscriptions on Checkout.
subscription_card_changeoptional
boolean Permit or restrict customer from changing the card linked to the subscription. You can also do this from the hosted page. Possible values:
true: Allow the customer to change the card from Checkout.
false (default): Do not allow the customer to change the card from Checkout.
false (default): You are not accepting recurring payments.
callback_urloptional
string Customers will be redirected to this URL on successful payment. Ensure that the domain of the Callback URL is whitelisted.
redirectoptional
boolean Determines whether to post a response to the event handler post payment completion or redirect to Callback URL. callback_url must be passed while using this parameter. Possible values:
true: Customer is redirected to the specified callback URL in case of payment failure.
false (default): Customer is shown the Checkout popup to retry the payment.
integer Sets a timeout on Checkout, in seconds. After the specified time limit, customer will not be able to use Checkout.
remember_customeroptional
boolean Determines whether to allow saving of cards. Can also be configured via the Razorpay Dashboard. Possible values:
true: Enables card saving feature.
false (default): Disables card saving feature.
readonly
object Marks fields as read-only.
contactoptional
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.
emailoptional
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.
nameoptional
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.
send_sms_hashoptional
boolean Used to auto-read OTP for cards and net banking pages. Applicable from Android SDK version 1.5.9 and above. Possible values:
true: OTP is auto-read.
false (default): OTP is not auto-read.
allow_rotationoptional
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.
retryoptional
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. Recommended to set this to 4. Having a larger number here can cause loops to occur.
configoptional
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 values:
en: English
ben: Bengali
hi: Hindi
mar: Marathi
guj: Gujarati
tam: Tamil
tel: Telugu
Handy Tips
If you call the payment start method from inside a fragment, ensure that the fragment's parent activity implements the PaymentResultListener interface.
You have the option to implement PaymentResultListener or PaymentResultWithDataListener to receive callbacks for the payment result.
PaymentResultListener provides only payment_id as the payment result.
PaymentResultWithDataListener provides additional payment data such as email and contact of the customer, along with the order_id, payment_id, signature and more.
Given below are the sample codes for implementation:
CopypublicclassMerchantActivityextendsActivityimplementsPaymentResultListener {
// ...@OverridepublicvoidonPaymentSuccess(String razorpayPaymentID) {
/**
* Add your logic here for a successful payment response
*/
}
@OverridepublicvoidonPaymentError(int code, String response) {
/**
* Add your logic here for a failed payment response
*/
}
}
CopyclassPaymentActivity: Activity(), PaymentResultListener {
// ...overridefunonPaymentError(errorCode: Int, response: String?) {
/**
* Add your logic here for a failed payment response
*/
}
overridefunonPaymentSuccess(razorpayPaymentId: String?) {
/**
* Add your logic here for a successful payment response
*/
}
CopypublicclassMerchantActivityextendsActivityimplementsPaymentResultWithDataListener {
// ...@OverridepublicvoidonPaymentSuccess(String razorpayPaymentID, PaymentData paymentData) {
/**
* Add your logic here for a successful payment response
*/
}
@OverridepublicvoidonPaymentError(int code, String response) {
/**
* Add your logic here for a failed payment response
*/
}
}
CopyclassPaymentActivity: Activity(), PaymentResultWithDataListener {
// ...overridefunonPaymentError(errorCode: Int, response: String?) {
/**
* Add your logic here for a failed payment response
*/
}
overridefunonPaymentSuccess(razorpayPaymentId: String?, PaymentData: PaymentData) {
/**
* Add your logic here for a successful payment response
*/
}
Watch Out!
Razorpay's payment process takes place in a new activity. Since there are two activities involved, your activity can get corrupted or destroyed if the device is low on memory. These two methods should not depend on any variables not set through your life cycle hooks.
It is recommended that you test everything by enabling "Don't Keep Activities" in Developer Options under Settings.
The SDK stores customer-specific data such as email, contact number, and user-session cookies if the customer wants to make another payment in the same session. You can delete such sensitive information before another customer logs into the app.
To erase customer data from the app, you can call the following method anywhere in your app.
CopyCheckout.clearUserData(Context)
Handy Tips
Contact our Support Team if you have any queries.
This is a mandatory step to confirm the authenticity of the details returned to the Checkout form for successful payments.
To verify the razorpay_signature returned to you by the Checkout form:
Create a signature in your server using the following attributes:
order_id: Retrieve the order_id from your server. Do not use the razorpay_order_id returned by Checkout.
razorpay_payment_id: Returned by Checkout.
key_secret: Available in your server. The key_secret that was generated from the Razorpay Dashboard.
Use the SHA256 algorithm, the razorpay_payment_id and the order_id to construct a HMAC hex digest as shown below:
Copygenerated_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 form, the payment received is from an authentic source.
Given below are the sample codes for payment signature verification.
Copy/**
* This class defines common routines for generating
* authentication signatures for Razorpay Webhook requests.
*/publicclassSignature
{
privatestaticfinalStringHMAC_SHA256_ALGORITHM="HmacSHA256";
/**
* Computes RFC 2104-compliant HMAC signature.
* * @param data
* The data to be signed.
* @param key
* The signing key.
* @return
* The Base64-encoded RFC 2104-compliant HMAC signature.
* @throws
* java.security.SignatureException when signature generation fails
*/publicstatic String calculateRFC2104HMAC(String data, String secret)throws java.security.SignatureException
{
String result;
try {
// get an hmac_sha256 key from the raw secret bytesSecretKeySpecsigningKey=newSecretKeySpec(secret.getBytes(), HMAC_SHA256_ALGORITHM);
// get an hmac_sha256 Mac instance and initialize with the signing keyMacmac= Mac.getInstance(HMAC_SHA256_ALGORITHM);
mac.init(signingKey);
// compute the hmac on input data bytesbyte[] rawHmac = mac.doFinal(data.getBytes());
// base64-encode the hmac
result = DatatypeConverter.printHexBinary(rawHmac).toLowerCase();
} catch (Exception e) {
thrownewSignatureException("Failed to generate HMAC : " + e.getMessage());
}
return result;
}
}
Copyimport (
"crypto/hmac""crypto/sha256""crypto/subtle""encoding/hex""fmt"
)
funcmain() {
signature := "477d1cdb3f8122a7b0963704b9bcbf294f65a03841a5f1d7a4f3ed8cd1810f9b"
secret := "qp3zKxwLZxbMORJgEVWi3Gou"
data := "order_J2AeF1ZpvfqRGH|pay_J2AfAxNHgqqBiI"//fmt.Printf("Secret: %s Data: %s\n", secret, data)// Create a new HMAC by defining the hash type and the key (as byte array)
h := hmac.New(sha256.New, []byte(secret))
// Write Data to it
_, err := h.Write([]byte(data))
if err != nil {
panic(err)
}
// Get result and encode as hexadecimal string
sha := hex.EncodeToString(h.Sum(nil))
fmt.Printf("Result: %s\n", sha)
if subtle.ConstantTimeCompare([]byte(sha), []byte(signature)) == 1 {
fmt.Println("Works")
}
}
After you have successfully completed the integration, you can set up webhooks, make test payments, replace test key with live key and integrate with other APIs.
You can use Razorpay 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 set up Webhooks.