Ramp Provider Rules: Crypto On-Ramps on Visa
Visa's ramp provider rules make the ramp liable for its conversion affiliates, ban stacking, and limit high-integrity risk registration to crypto only.
By Jeffrey Anderson

- A ramp provider is registered by its acquirer as a third party agent with Visa. It is not a merchant category or a licence you apply for, and the registration obligation sits on the acquirer.
- The businesses underneath are Conversion Affiliates, not sponsored merchants. Section 5.3.5.1 (ID# 0031033) requires the ramp provider to contract with each one before depositing any transactions on it.
- The ramp provider is liable for all acts, omissions, cardholder disputes and customer service issues of its affiliates, and financially liable for each transaction processed on their behalf.
- Neither the ramp provider nor its affiliates may transfer that liability by asking cardholders to waive dispute rights. Both halves are written out separately.
- No stacking. A ramp provider must not deposit transactions for another ramp provider, a payment facilitator or a staged digital wallet, and the acquirer must ensure it does not contract with a facilitator or staged wallet operator.
- Cross-border is allowed but three jurisdictions must be legal, not two: the ramp provider's, the conversion affiliate's, and the cardholder's. The third is the one most builds ignore.
- Section 5.3.5.2 (ID# 0031031), revised in the 24 October 2026 edition, limits the high-integrity risk route to affiliates converting to or from a non-fiat currency. It is not a general structure for other high-risk categories.
- Both the ramp provider identifier and the conversion affiliate identifier go in the authorization record, but only the ramp provider identifier goes in the clearing record.
- The acquirer itself must be in good standing in all Visa risk management programs and financially sound as determined by Visa before it can contract with a ramp provider.
Ramp provider is the Visa entity type for a crypto on-ramp, and it carries its own rulebook section that almost nobody in the space has read. The businesses underneath a ramp provider are not called sponsored merchants. They are Conversion Affiliates, and the distinction decides who is liable for what.
Two sections govern it. Section 5.3.5.1 (ID# 0031033) of the Visa Core Rules and Visa Product and Service Rules sets what must be in the agreement. Section 5.3.5.2 (ID# 0031031) sets what the acquirer must do, and it was revised in the 24 October 2026 edition.
A Ramp Provider Is Registered as a Third Party Agent
Start with the registration, because it determines everything downstream. The acquirer must "Register the Ramp Provider as a Third Party Agent with Visa".
So a ramp provider is not a merchant category or a licence you apply for. It is an agent registration your acquirer performs, with the acquirer carrying the obligation. That brings the whole third party agent registration regime with it.
The acquirer also has to qualify itself. It must be in good standing in all Visa risk management programs and financially sound as determined by Visa. If your acquirer is sitting in a risk programme, it cannot take you on.
The Liability Runs to the Ramp Provider
The agreement has to say so explicitly. The ramp provider "Is liable for all acts, omissions, Cardholder disputes, and other Cardholder customer service-related issues" caused by its conversion affiliates, and is responsible and financially liable for each transaction processed on their behalf.
It also has to contract with each affiliate first. The requirement is "A requirement that the Ramp Provider enter into a contract with each Conversion Affiliate before it deposits Transactions on the Conversion Affiliate." Before, not alongside.
And the liability cannot be pushed onto the cardholder. The ramp provider must not transfer or attempt to transfer its financial liability by asking cardholders to waive their dispute rights, and must not permit a conversion affiliate to do it either. Both halves are written out, which tells you Visa expects the attempt.
No Stacking
One prohibition closes the structure off from the rest of the ecosystem. A ramp provider "Must not deposit Transactions on behalf of another Ramp Provider, Payment Facilitator, or Staged Digital Wallet."
The acquirer carries the mirror image: it must ensure the ramp provider does not contract with a payment facilitator or staged digital wallet operator to process transactions.
So you cannot chain a ramp into a payment facilitator or a staged wallet, in either direction. Compare that to the facilitator model, where the equivalent question is about the direct agreement threshold rather than a flat ban on stacking.
A ramp provider also must not knowingly contract with "a retailer whose contract to accept Transactions was terminated at the direction of Visa or a government agency".
Three Legalities, Not One
Cross-border is permitted and the condition attached to it is the sharpest thing in the section.
A ramp provider may process for conversion affiliates located in a different country, and must ensure transactions are legal in the country of the ramp provider and of the conversion affiliate. The acquirer requirement goes one further. Its risk controls must "Prevent Transactions that are illegal in the location of the Ramp Provider", the location of the conversion affiliate, and the location of the cardholder.
Three jurisdictions, and the cardholder's is the one nobody designs for. A compliant transaction between a ramp in one country and an affiliate in another can still be prohibited because of where the buyer is sitting.
The same controls must "Prevent the sale of counterfeit products or goods that infringe on intellectual property" and "Provide a process to investigate and remediate rights-holder complaints", plus compliance with anti-money laundering and anti-terrorist financing requirements.
The High-Integrity Risk Route Is Crypto Only
This is the line worth reading twice if you are building anything adjacent.
Where a ramp provider supports a conversion affiliate that Visa classifies as high-integrity risk, the ramp provider must be registered as a High-Integrity Risk Ramp Provider and the affiliate must also be registered as a High-Integrity Risk Merchant before submitting transactions. Then the rule adds: "For the avoidance of doubt, only Conversion Affiliates that are converting Transactions to/from a non-fiat currency (for example: cryptocurrency) are allowed."
Read in context, that sentence confines the high-integrity risk ramp route to currency conversion. It is not a general-purpose structure for other high-risk categories to sit under. If an affiliate is high-integrity risk and is not converting to or from a non-fiat currency, this is not the route for it.
The wider programme those registrations attach to is covered in our piece on the Visa Integrity Risk Program.
Both Identifiers in Authorization, One in Clearing
The data requirement is small and easy to get wrong.
The acquirer obtains a unique ramp provider identifier from Visa and assigns it. The ramp provider assigns a unique identifier to each conversion affiliate. Every transaction then carries both in the authorization record, and "In a Clearing Record, only the Ramp Provider identifier".
That asymmetry matters for reconciliation. At clearing, the network record identifies the ramp, not the affiliate, which is the same shape as the facilitator model and the same reason attribution has to be solved in your own books.
Brazil has its own variant, where the acquirer sends the tax identification and merchant legal name if the ramp provider has consented, and the two identifiers if it has not.
What Else Lands on the Ramp Provider
Three smaller obligations round out the agreement.
It must deposit transactions only for conversion affiliates of goods and services that use its services under a contract. It must provide the names of its affiliates' principals and their country of domicile, plus transaction reports, to the acquirer and to Visa on request. And where the ramp provider delivers payment information to conversion affiliates, it must ensure they comply with the PCI Software Security Framework, which sits alongside the ordinary PCI DSS obligations rather than replacing them.
The acquirer must also ensure the ramp provider uses the appropriate MCC for each conversion affiliate, which is where this connects to the quasi-cash and gambling indicator rules that decide how a conversion transaction gets coded.
FAQ
What is a ramp provider under the Visa rules?
An entity registered by its acquirer as a third party agent that processes transactions on behalf of conversion affiliates, which are businesses converting to or from a non-fiat currency such as cryptocurrency.
How is it different from a payment facilitator?
The businesses underneath are conversion affiliates rather than sponsored merchants, and the stacking rules differ. A ramp provider must not deposit transactions for another ramp provider, a payment facilitator or a staged digital wallet, and the acquirer must ensure it does not contract with a facilitator or staged wallet operator.
Who is liable for a conversion affiliate's disputes?
The ramp provider. The agreement must state that it is liable for all acts, omissions, cardholder disputes and customer service issues, and financially liable for each transaction processed on an affiliate's behalf.
Can a ramp provider serve affiliates in other countries?
Yes. It must ensure the transactions are legal in its own country and the affiliate's, and the acquirer's controls must also prevent transactions illegal where the cardholder is located.
Does a ramp provider need high-integrity risk registration?
Only where it supports an affiliate Visa classifies as high-integrity risk. Both the ramp provider and the affiliate must then be registered before transactions are submitted, and the rule limits that route to affiliates converting to or from a non-fiat currency.
What identifiers have to be in the transaction?
Both the ramp provider identifier and the conversion affiliate identifier in the authorization record, and only the ramp provider identifier in the clearing record.
Does the ramp provider have to contract with each affiliate?
Yes, and before depositing any transactions on that affiliate. The acquirer must separately ensure the contract exists.
Do normal merchant rules still apply?
Yes. The acquirer must ensure the ramp provider complies with all Visa rules relating to merchants, except where a rule is inconsistent with one specific to ramp providers.
Jeffrey Anderson, Merchant Placement Specialist
Merchant placement specialist at Gray Merchants. Jeffrey works directly with acquiring-bank underwriting teams across the firm’s 70+ banking relationships to place high-risk and hard-to-place businesses, structure multi-MID accounts, and keep flagged merchants processing. His writing draws on the placement files he works every week: what underwriters ask for, why accounts get declined, and what keeps an approved account open.