S2S (Seamless API) API Documentation
Integrate approved PayOrc server-to-server transaction types, wallets, token payments, order retrieval, and payment management.
Use this section to understand and implement PayOrc S2S (Seamless API) capabilities through the relevant public integration flows and API references.
S2S (Seamless API) Guides
Transaction Types
Server-to-Server (S2S) payment processing - transaction types, MOTO, CAUTH, SADAD, and 3D Secure handling.
S2S Payment
Server-to-Server (S2S) payment processing using the standard Payment method with card details.
CAUTH (Pay by Token)
Charge an approved saved payment token through PayOrc using the CAUTH server-to-server transaction class.
MOTO
Merchant-initiated transactions for phone or mail orders where the merchant enters card details on behalf of the customer.
S2S Manage Payment
Capture, void, refund, and retrieve approved PayOrc server-to-server payment transactions.
S2S Fetch Order
Retrieve server-to-server order and transaction details using the corresponding PayOrc order identifier.
SADAD Bank Transfer
Process direct bank transfers via the SADAD payment network for Saudi Arabia.
URPay
Process approved server-to-server mobile-wallet payments through the PayOrc URPay integration.
STC Pay
Process approved mobile-wallet transactions through the PayOrc server-to-server STC Pay integration.
Tabby
Process approved Buy Now, Pay Later transactions through the PayOrc server-to-server Tabby integration.
Apple Pay
Accept Apple Pay on S2S with type APPLE_PAY — pass the device wallet token in data.token, no card_details required.
Google Pay
Accept Google Pay on S2S with type GOOGLE_PAY — pass the client wallet token in data.token.
Integration Guidance
- Authenticate requests only from a secure server environment.
- Validate required fields and supported values before sending each request.
- Store PayOrc and merchant references for status tracking and reconciliation.
- Confirm asynchronous outcomes through the documented webhook or status API where applicable.
- Exercise the complete flow with approved test credentials before production use.
Provider availability, credentials, and production enablement depend on merchant approval and the applicable PayOrc agreement.