Payment Service API › Take Payment

Take Payment

Charge a previously-stored card token without the customer present.

API reference menu

When to use this

You already have a gateway customer ID from a prior payment. Use it to charge again — renewals, outstanding balances, pre-authorised transactions.

Endpoint

POST https://accounts.paytia.com/api/payment_service

Try it

Paste your sandbox key, edit any field, and hit Execute. Nothing is stored — the key travels to the Paytia proxy and the response comes straight back.

Try it
POST https://accounts.paytia.com/api/payment_service

Sandbox or live key — nothing is stored.

String: Required field cus_value (Stripe) or thiswill be the unique transaction ID of your account gateway in the case of type= reserve_settle or remove. If the type is set to store_payment then this will be the token ID of transaction.

Decimal: A numeric value for the transaction gross charge stated to two decimal places

String: Invoice Reference Number (this field is mapped and passed to the final payment gateway connector in ) for referencing the order. Note: on some payment gateways this is unique field meaning the payment gateway will reject repeat values that are not unique).

String value - Required field - Allows you to complete a validation, Reserve, and Capture payment type Supported values remove - this removes a Reserve Pre-Auth set on a card reserve_settle - Completes a Reserve Pre-Auth charge for the amount sent. Works with the Stripe pi_ value returned in the transaction post API. store_payment - works with a (Stripe) pm_ value. Card on file payment processed. cancel - cancels a subscription update - updates a subscription

curl
curl --location --request POST 'https://accounts.paytia.com/api/payment_service' \
  --header 'X-API-KEY: YOUR_API_KEY' \
  --form 'transaction_id={cus_ value or transaction ID}' \
  --form 'amount=0.00' \
  --form 'reference_number={ADD A UNIQUE REFERENCE NUMBER}' \
  --form 'type=store_payment'
Response
No response yet. Paste your key, tweak the values, and click Execute.

Fields

Full field-by-field reference below. Required vs optional varies by flow — the try-it explorer above starts with sensible defaults.

FieldTypeDescription
transaction_idtextString: Required field cus_value (Stripe) or thiswill be the unique transaction ID of your account gateway in the case of type= reserve_settle or remove. If the type is set to store_payment then this will be the token ID of transaction.
amounttextDecimal: A numeric value for the transaction gross charge stated to two decimal places
reference_numbertextString: Invoice Reference Number (this field is mapped and passed to the final payment gateway connector in ) for referencing the order. Note: on some payment gateways this is unique field meaning the payment gateway will reject repeat values that are not unique).
typeselectString value - Required field - Allows you to complete a validation, Reserve, and Capture payment type Supported values remove - this removes a Reserve Pre-Auth set on a card reserve_settle - Completes a Reserve Pre-Auth charge for the amount sent. Works with the Stripe pi_ value returned in the transaction post API. store_payment - works with a (Stripe) pm_ value. Card on file payment processed. cancel - cancels a subscription update - updates a subscription

Next

Ready to build with Paytia?

The docs are open. Keys are gated — drop us a line and we'll issue sandbox credentials so you can try every flow against a real endpoint.