Configurations

Test Mode: It is designed specifically for development, quality assurance, and training purposes, providing a risk-free environment where transactions use virtual funds and have no real financial impact. In this mode, developers can utilize test API keys, simulate various payment scenarios (including successes, failures, and pending states), and experiment with different bank and card test cases without moving real money.

Production Mode: It is where actual business transactions occur, involving real money and customer interactions. Activated by switching to live API keys. This mode enforces real-world constraints such as transaction limits; Unlike Test Mode, Production Mode processes authentic payouts, generates real financial records, and requires rigorous monitoring for security and performance.

Keys

API keys: serve as unique identifiers that authenticate your application when interacting with AdmasPay's APIs. These keys are included in request headers to authorize access to payment processing, transaction queries, and other gateway functions. They operate like digital signatures, validating that requests originate from trusted sources while enforcing access controls and usage limits.

Encryption keys: are cryptographic instruments that secure data confidentiality and integrity during transmission and storage. AdmasPay employs them to encrypt sensitive payment details, authenticate webhook payloads via digital signatures, and establish secure TLS connections.

Charge Payer Options

AdmasPay allows flexible configuration of who bears the payment processing fees. There are three possible settings:

• CUSTOMER Pays
  • Processing fees are added to the transaction amount
  • Customer pays the full amount (product price + fees)
• MERCHANT Pays
  • Processing fees are deducted from the merchant's settlement
• BOTH Shares (Split Fees)
  • Fees are divided between customer and merchant