Authentication and environments
Related
B2B Payments runs on the Payments API and uses its keys. This page covers the hosts and how each kind of call identifies the seller.
Hosts
Contracts use the Payments API hosts: https://sandbox.payme.io/api for testing and https://live.payme.io/api for production. Contract endpoints are under /payment-contracts.
Transfer funds between sellers uses the same hosts.
Contract calls
Every contract call identifies the seller by its seller_payme_id (MPL) in the PayMe-Merchant-Key header. On POST /payment-contracts you can send seller_payme_id in the JSON body instead; the file endpoints (…/invoices) read the header only. Partners can also send their client key in the PayMe-Partner-Key header. A contract call with no key at all fails with error 1 and HTTP 500 (status_additional_info payme_client_key). With a partner key but no seller key, it fails with error 1 and HTTP 400 (status_additional_info seller_payme_id). The file endpoints fail with error 251 and HTTP 400 when the PayMe-Merchant-Key header is missing. See Payments Authentication and environments for the keys themselves.
Wallet transfers
Transfer funds between sellers is authenticated by seller_payme_id in the body: the MPL of the seller that receives the funds. Partners also send their payme_client_key in the body, and both sellers must belong to that partner.