The Significance Of ARN Number In Mutual Funds
Individual intermediaries receive a photo identity card which comprises of the Application Reference Number or ARN, the validity period of the ARN, and the address of the intermediary. Corporates receive a registration letter with ARN code, the validity of ARN code, and name of the corporate, whilst their employees get an EUIN card with the same details.
The Requirement?
Well, the line states that- Mutual funds are subject to market risks, but that doesn’t mean one cannot reduce risk by diligence. Therefore, an intermediary is obliged to educate & inform the investor about all the risks involved. Doing this will safeguard the interests of all the parties that are involved in the transaction.
AMFI (Association of Mutual Funds) and SEBI take several measures for ensuring the safety of investors. One of the steps includes the mandatory procurement of ARN code for distributors.
How to get ARN code?
The following process:
- Intermediaries should apply in a systematic form; It is available both online & offline at the offices of CAMS and AMFI.
- Submit your application form along with KYD acknowledgment (Knowing Your Dealer). After applying, the individual should present KYD application form personally.
- The intermediary should submit the NISM certificate copy, PAN card copy, bank account proof, Aadhaar card copy, & two passport size photographs.
- The fees & the documentation will differ for corporates & other entities. Check the details before applying.
Any Benefits of ARN number in mutual funds?
ARN code is important for both the investor and the intermediary. Basically, it’s like an ID of the investor/intermediary. It is used to track down the assets mobilized by the intermediary. Also, you can use it to calculate the brokerage of the intermediary. In short, the intermediary will become eligible to distribute mutual funds only if they have (received) ARN number.
“Are you looking to invest? How about opening your account with Gulaq & start investing in Direct Mutual Funds? Get in touch.”
*Mutual fund investments are subject to market risks. Please read the scheme information and other related documents carefully before investing.
What is an AWS ARN and Why is it Important?
When using AWS, you’ll often stumble upon obscure strings that start with arn . You may be wondering what these strings are and what role they play in AWS. In this article, you’ll learn exactly that.
So let’s get into it.
What is an AWS ARN?
An ARN stands for Amazon Resource Name. It is a unique identifier of a resource that you create in AWS. In other words, anything that you create in AWS typically has an ARN associated with it.
Keep in mind that there are some exceptions to this. For example, when you create a DynamoDB table, it will have an ARN associated with it. However if you insert an item/record into DynamoDB, no ARN will be created.
A general rule of thumb is that if you ever go into the AWS console and click the “create” button, there will be an ARN identifier associated with it.
What Does an ARN Look Like?
An ARN takes the following form:
Lets look at each of these items independently.
- partition – a partition is a group of AWS regions. There are three possible values for this component, either aws , aws-cn or aws-us-gov . 99% of you will only ever see/use ARNs that use the aws value.
- service – the service represents which service this ARN is with reference to. For example, if you create a DynamoDB table, your service identifier will be dynamodb . For S3 , it would be s3 , and for Lambda it would be lambda – I think you get the idea.
- region – the region is the geographic region that the resource was created in. There are many regions across AWS all across the world. Some popular ones include us-east-1 , eu-west-1 , and us-west-2 . Remember that resources you create are scoped to a particular region. In other words, a DynamoDB table created in us-east-1 exist only in that region and not others. The resource itself is hosted in the associated data center of that region.
- account id – every AWS user has an account id. An account id is simply a 12 digit number that uniquely identifies your account.
- resource type – the resource type is an optional field. Depending on the resource you create, it may or may not be present. In the above example, you can see it is the value table for our DynamoDB table. This is because the ARN is for a service subresource (a table). This only makes sense in some contexts and is not present in all ARNs.
- resource id – the resource id represents the lowest level resource. In the above example it represents the name of our DynamoDB table – Countries .
More ARN Examples
It’s important to remember that ARNs take a similar form, but look slightly different depending on the AWS service. Here are some examples of what ARNs look like across a multitude of AWS services.
- Lambda Function – arn:aws:lambda:us-east-1:755314965794:function:Disconnect
- S3 Bucket – arn:aws:s3. beabetterdev-demo-bucket
- SNS Topic – arn:aws:sns:us-east-1:755314965794:DemoTopic
- SNS Topic Subscription – arn:aws:sns:us-east-1:755314965794:DemoTopic:01b9251e-e8c4-4ece-9e6a-6c20492d768e
- Cloudwatch Alarm – arn:aws:cloudwatch:us-east-1:755314965794:alarm:5min_3of5_TicktockFunction
- IAM User – arn:aws:iam::755314965794:user/amplify-XzaOi
These are all real AWS ARNs from my personal AWS account. Hopefully you get the picture of what they look like.
ARN Paths
ARNs can also have paths associated with them to capture multiple AWS resources. For example, if we were working with an S3 bucket and wanting to give IAM permissions to a user to read access files only in a specific S3 bucket, we could use this form:
ARNs can contain paths that refer to sub-resources of a specific resource – in this case, all objects within the myTestBucket will be accessible to the user.
This is a handy feature that makes assigning permissions much easier. Instead of having to create many many policies for each objects, we can simply use paths and wildcards (the * in this case) to indicate all. The same principle applies for other AWS resources such as DynamoDB tables (we can say arn::xxx:table/*) to give access to ALL tables.
Why are ARNs Useful?
Often times we need to connect AWS resources together. For example, if we were to try and subscribe a SNS topic to a Lambda function, we would need to provide our ARN to tell AWS which Lambda function we would like subscribed to our SNS topic.
Since all ARNs are unique, this allows AWS to distinguish which resource to link to the topic. You can see an example in the AWS console of us trying to subscribe one of our Lambda functions to our SNS.
Using an ARN to link a Lambda Function to an SNS topic.
As you can imagine, there are many different ways to link resources together in AWS. This is just one example, but the principle remains the same. You must provide the specific ARN of the resource you would like to link.
Where Do I Find A Resource’s ARN?
Unfortunately each AWS service is different, and there is no one centralized place that ARNs are located. However, there are some general patterns that AWS follows to display your ARN.
Typically, you will find your ARN on the home page of a resource. If you can’t find it there, you’ll probably find it under the under the “Additional Info” (or some phrase similar) of the AWS console. For example, below is the location of the ARN of a Lambda function in my AWS account.
A Lambda Function’s ARN is located on the home page of the function.
In other cases such as a DynamoDB table, the ARN can be a bit more challenging to find. In this case, we need to first click on the DynamoDB Table, followed by clicking Additional info before we can find the ARN. An image of this can be seen below.
A DynamoDB Table’s ARN requires a couple more clicks to find. First click the table name, followed by clicking Additional info as seen in this image.
Can You Update an ARN?
To put it simply, No. ARNs are immutable and cannot be changed. In order to rename a resource, you need to delete the resource and re-create it. A bit cumbersome, but that’s how it works.
Wrap Up
ARNs or Amazon Resource Names are unique strings that identify an AWS resource or group of AWS resources via a path. You’ll see them all over AWS and its important to understand what they are and how they work. ARNs can not be modified after creation. They are typically located in the home page of the AWS resource or under “Additional Settings” pages.
What is an ARN (Acquirer Reference Number)?
Acquirer Reference Numbers (ARNs) are unique 23-digit numbers. They are linked to online Visa and Mastercard debit and credit card transactions between a merchant’s bank (the acquiring bank) and a cardholder’s bank (the issuing bank). An ARN is created when a transaction flow takes place via a payment gateway. The reference numbers instill confidence in online payments because transactions can be traced and verified as they move through payment flows.
What are ARNs used for?
By creating more transparency, ARNs help to prevent fraud and unauthorized transactions. They give buyers a better online buying experience and the same reassurances that they would receive when making offline purchases. The unique acquirer reference number means a transaction can be tracked and checked in order to reveal any errors or irregularities. This is useful as refund transactions can take time to process so having insight into what is happening during this process is important. If a refund is delayed or fails to process, the unique number will help your bank to trace the refund.
Apart from being assigned to debit and credit card transactions for online purchases, ARNs are used to verify electronic funds transfer, partial settlements, and transfer of funds.
To learn more about how we can help your business improve acceptance rates and optimize your payments strategy visit our payment processing solutions page. Alternatively, you can read one of the many case studies our customers have shared with us, to learn from their experiences of partnering with Checkout.com.
How to track an ARN number for refund management
One of the main reasons a merchant may need to check an ARN number is to manage customer refunds if there is an issue with a purchase. For example, a customer may not be satisfied with the quality or condition of the purchase or has failed to receive the goods, which is where an ARN comes in to log the refund from the merchant.
For refunds via debit or credit cards, payment (ie, the refund) can be made directly to the card used for the transaction. If a customer wants to know when the refund will be made, it is easy to track the payment flow using the ARN number. Both the issuing bank (the customer’s bank) and the acquiring bank (the merchant’s bank) can access the number to trace a transaction. Either party can share the information with the customer.
How to find an ARN number
Merchants can obtain ARN numbers from their payment providers, and the numbers usually appear with information showing the status of a transaction. For example, if it is processing or a number hasn’t been assigned yet because the charge hasn’t been processed. The status information is expressed as follows:
- ARN is not available – this is displayed when the refund has been completed. The payment processor will reverse the payment authorisation and remove the charge, so the refund is made before the charge is processed with the bank
- ARN is processing – this indicates that the refund transaction is taking place but has yet to complete
- ARN is available – this is when the acquirer reference number appears within the refund
When you use Checkout.com for payment processing, the ARN associated with each transaction can be accessed via the Checkout.com Dashboard and can help to manage disputes if a customer queries a transaction with their card issuer. Access to the ARN via the Checkout.com Dashboard allows you to monitor and respond to disputes quickly and easily.
Why ARN is good for both merchant and customer
Here’s why ARNs are good for both merchants and customers:
Better customer experience: ARNs improve customer experience by providing a more transparent and efficient refund process. Allowing your customer to track the status of their refund with an ARN reduces their frustration, avoids unnecessary back and forth, and ensure that they receive their refund promptly
Reduced fraud: ARNs can reduce fraud by providing a way to track and identify fraudulent transactions. For example, if you experience a chargeback, you can submit the ARN to the bank, who can use it to investigate the legitimacy of the transaction, help to identify and prevent fraudulent transactions from occurring
More efficient: by providing a way to track and manage transactions, ARNs can increase efficiency. For example, it can be difficult for merchants to keep on top of a large number of transactions at once. However, with ARNs, you can easily identify and track each transaction, which can help to streamline your operations
How Checkout.com helps you track transactions with ARN
When you use Checkout.com for payment processing, the ARN associated with each transaction can be accessed via the Checkout.com Dashboard and can help to manage disputes if a customer queries a transaction with their card issuer. Access to the ARN via the Checkout.com Dashboard allows you to monitor and respond to disputes quickly and easily.
Most Recent Articles
Understanding identity fraud to better defend your business
In a rapidly evolving world driven by remote work and digital connectivity, we’ve unlocked a range of services that revolutionize the way we operate. While this digital transformation has.
KYC verification explained
KYC verification is ensuring secure transactions and preventing fraud. Read about sectors it can be used, documents needed and much more.
Introducing Intelligent Acceptance: Solving the $50.7 billion payment performance problem
Solving the $50.7 billion payment performance problem.
Maximize payments efficiency: 5 ways a unified platform can help US businesses
Payments can be complex, especially when layered onto fragmented legacy systems. This complexity often makes upgrading these systems too costly and time-consuming for businesses in need of rapid.
The future of US real-time payments ahead of FedNow launch
While advancements in the US payments landscape have emerged, they have mostly addressed the front-end of the payments experience. The foundational infrastructure is still in need of an upgrade.
Is US payments fraud becoming “too big to fight”?
Innovation in the US has brought about significant changes and advancements across various industries, but it has also paved the way for new avenues of fraudulent activities. The Federal Trade.
What do real-time payments mean for merchants?
Efficient and secure real-time payments for seamless transactions. Experience instant fund transfers with our advanced payment solutions
Payment links: what they are and how they work
Learn what payment links are, how they work, and explore how you can use them to start requesting payments for your business
Card not present fraud: Know the prevention measures
Learn how card-not-present fraud works, the common statistics, and how to introduce the right CNP fraud prevention measures at Checkout.com
How to prevent buy now, pay later (BNPL) fraud
Find out what Buy Now, Pay Later (BNPL) fraud is, how it works and ways to detect and prevent it in your business practices
What is a digital wallet?
Learn what a digital wallet is, how it works and what the benefits of accepting this as a payment method are for your business
What is a BIN attack?
Shield your online business from credit card fraud using our BIN attack guide. Uncover their workings, recognize them, and protect yourself.
How to win credit card disputes
Discover the process behind successful dispute resolution, and how merchants can win credit card disputes with Checkout.com
2FA vs. MFA in payments
Explore the differences between 2FA and MFA in payments, and the benefits and security aspects of each authentication method for secure payment processing
What are payment rails?
Discover the importance of payment rails, learn about the different types and how to find the right choice for your business.
Intelligent payment routing explained
Learn more about intelligent payment routing and the different use cases and benefits it can bring for merchants.
Why payments teams must own their customers’ pains, with Logan Vander Linden from Expedia Group
Logan Vander Linden explains why payments are essential to the traveler's experience and why getting it right means thinking about the big picture.
What is RBA (Risk Based Authentication) in payments?
Risk Based Authentication is part of 3D Secure payments. Read how RBA can help you benefit from frictionless transactions.
A guide to marketplace payments
Learn how marketplace payments work and discover how to choose the best payment options for your online marketplace with Checkout.com
How to improve payment conversion with delegated authentication
Learn about delegated authentication and how it can benefit your conversions in online payments.
What is an ARN
In the last chapter while we were looking at IAM policies we looked at how you can specify a resource using its ARN. Let’s take a better look at what ARN is.
Here is the official definition:
Amazon Resource Names (ARNs) uniquely identify AWS resources. We require an ARN when you need to specify a resource unambiguously across all of AWS, such as in IAM policies, Amazon Relational Database Service (Amazon RDS) tags, and API calls.
ARN is really just a globally unique identifier for an individual AWS resource. It takes one of the following formats.
Let’s look at some examples of ARN. Note the different formats used.
Finally, let’s look at the common use cases for ARN.
ARN is used to reference a specific resource when you orchestrate a system involving multiple AWS resources. For example, you have an API Gateway listening for RESTful APIs and invoking the corresponding Lambda function based on the API path and request method. The routing looks like the following.
We had looked at this in detail in the last chapter but here is an example of a policy definition.
ARN is used to define which resource (S3 bucket in this case) the access is granted for. The wildcard * character is used here to match all resources inside the Hello-bucket.
Next let’s configure our AWS CLI. We’ll be using the info from the IAM user account we created previously.
For help and discussion
SST Guide
Download the FREE 1000 page ebook!
Get the most popular resource for building serverless apps. We’ll also send you updates when new versions are published.