API Docs
AML Policy
Cookies Policy
Confidentiality & Data Protection Policy
API Docs
The most optimal integration option with us:
1. Use both S2S and HPP flows as described in our API documentation: https://api.payadmit.com/docs/
All HPP methods function in the same way, with only slight differences in the required fields and method names in the requests.
2. Additionally, for all methods and flows, it is essential to implement player statistics tracking.
This allows us to optimize traffic routing on our side. Details can be found in the attached file and the API documentation.
If implementing this flow is not feasible, you may use one of the alternative traffic segmentation methods described in the same file.
3. We require a mandatory set of fields on our end.
However, some providers may have additional required fields depending on the payment method. Below is the basic field set, which covers the majority of providers:
card
object (for S2S card transactions)
description
amount
currencyCode
email
ip
phone
firstName
lastName
dateOfBirth
country
city
zip
state
addressLine1
By implementing the points above, you’ll be able to seamlessly integrate with most providers and payment methods already supported by PayAdmit, with no further development required.
API Docs
AML Policy
Cookies Policy
Confidentiality & Data Protection Policy
API Docs
The most optimal integration option with us:
1. Use both S2S and HPP flows as described in our API documentation: https://api.payadmit.com/docs/
All HPP methods function in the same way, with only slight differences in the required fields and method names in the requests.
2. Additionally, for all methods and flows, it is essential to implement player statistics tracking.
This allows us to optimize traffic routing on our side. Details can be found in the attached file and the API documentation.
If implementing this flow is not feasible, you may use one of the alternative traffic segmentation methods described in the same file.
3. We require a mandatory set of fields on our end.
However, some providers may have additional required fields depending on the payment method. Below is the basic field set, which covers the majority of providers:
card
object (for S2S card transactions)
description
amount
currencyCode
email
ip
phone
firstName
lastName
dateOfBirth
country
city
zip
state
addressLine1
By implementing the points above, you’ll be able to seamlessly integrate with most providers and payment methods already supported by PayAdmit, with no further development required.
API Docs
AML Policy
Cookies Policy
Confidentiality & Data Protection Policy
API Docs
The most optimal integration option with us:
1. Use both S2S and HPP flows as described in our API documentation: https://api.payadmit.com/docs/
All HPP methods function in the same way, with only slight differences in the required fields and method names in the requests.
2. Additionally, for all methods and flows, it is essential to implement player statistics tracking.
This allows us to optimize traffic routing on our side. Details can be found in the attached file and the API documentation.
If implementing this flow is not feasible, you may use one of the alternative traffic segmentation methods described in the same file.
3. We require a mandatory set of fields on our end.
However, some providers may have additional required fields depending on the payment method. Below is the basic field set, which covers the majority of providers:
card
object (for S2S card transactions)
description
amount
currencyCode
email
ip
phone
firstName
lastName
dateOfBirth
country
city
zip
state
addressLine1
By implementing the points above, you’ll be able to seamlessly integrate with most providers and payment methods already supported by PayAdmit, with no further development required.