saudi-pay

Unify Saudi payment gateways into a single integration workflow.

1|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/jackquelinunpredictable827/mkhlab --skill saudi-pay-jackquelinunpredictable827
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: saudi-pay
Source: https://github.com/jackquelinunpredictable827/mkhlab/tree/main/hermes-skills/saudi-pay
Command: npx skills add https://github.com/jackquelinunpredictable827/mkhlab --skill saudi-pay-jackquelinunpredictable827

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Saudi payment integrations often require custom adapters for each gateway, leading to duplicated logic and inconsistent customer experiences. This Skill unifies multiple Saudi gateways under a single integration pattern, simplifying onboarding and maintenance.

Core Features & Use Cases

  • Unified gateway support for Moyasar, Tap, HyperPay, PayTabs, Tabby, Tamara, and STC Pay.
  • Configurable test environment with sandbox credentials and example curl commands.
  • End-to-end payment flows from initiation to confirmation across multiple providers.

Quick Start

Configure your sandbox keys and run the example curl commands to start a payment.

Frequently Asked Questions about saudi-pay

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I integrate multiple Saudi payment gateways without duplicating logic?

You can integrate multiple Saudi payment gateways by applying a unified developer workflow pattern across Moyasar, Tap, HyperPay, PayTabs, Tabby, Tamara, and STC Pay, eliminating duplicated custom adapter logic and ensuring consistent transaction processing.

How do I test Saudi payment gateway integrations safely using curl?

Saudi payment gateway testing is performed safely by running example curl commands with configurable sandbox and test credentials, allowing you to validate end-to-end payment flows from initiation to confirmation without processing real transactions.

Do I need environment variables for API keys when processing Saudi payments?

Yes, Saudi payment processing requires environment variables to securely manage API keys for supported gateways like Tabby and Tamara, ensuring credentials are safely configured for both sandbox testing and live transaction environments.

Does this unified payment integration support Tap and Moyasar for back-end services?

Yes, the unified payment integration supports back-end services and apps requiring gateway selection and transaction testing across Tap, Moyasar, HyperPay, PayTabs, Tabby, Tamara, and STC Pay for the Saudi Arabia market.

What is the best way to manage gateway selection for Saudi Arabia payment processing?

The best way to manage gateway selection for Saudi Arabia payment processing is to use a unified integration pattern that abstracts provider-specific differences into a single workflow, simplifying onboarding and maintenance across multiple gateways.