Update a payment

post/payments/{id}

The POST /payments/{id} call allows your platform to update and add custom data to a payment.

SecurityappIdAuth and appTokenAuth
Request
path Parameters
id
required
string [ 1 .. 255 ] characters
header Parameters
Api-Version
required
string
Example: 3.0
Content-Type
required
stringapplication/json
Example: application/json
Unique-Key
string
Request Body schema: application/json
object or null

For Card Present, we allow adjusting the amounts to greater or less than the auth amount. For Card Not Present, we allow adjusting the amounts to less than the auth amount for delayed capture only.

capture_at
integer or null

Designate the time at which this payment will capture using a UNIX epoch timestamp. The capture time cannot be more than 7 days in the future. Note that epoch timestamps use the UTC timezone.

object or null

Any custom data your platform chooses to attach to this resource. The custom data must be key-value pairs and not contain any personally identifiable information (PII) or payment card (PCI) data.

Array of objects or null

Any rbit data your platform chooses to attach to this resource. The rbit data must be key-value pairs and can be an array of rbit objects.

reference_id
string or null [ 1 .. 255 ] characters

A custom reference ID for your platform to track the object. It can be any string.

Responses
200
Response Schema: application/json
id
required
string [ 1 .. 255 ] characters

ID of the object or resource.

resource
required
string

Helps organize information by identifying the resource type of the object data.

Value: Description
payments
path
required
string

The HTTP path of the resource. The path can be used to retrieve details about the resource and perform actions on it.

required
object or null

Details the owner resource and owner path.

create_time
required
integer <int64> >= 0

The UNIX timestamp for when the object was created.

status
required
string
Enum: Description
pending

This payment is processing, but is not yet included in the account's available or reserve balance. Find more information in the pending_reasons structure.

completed

This payment has finished processing, and is now available in either the account's available or reserved balance. Note: A payment can have a completed status and simultaneously have a refund or dispute issued against it.

… 2 more
amount
required
integer
amount_refunded
required
integer
amount_disputed
required
integer
currency
required
string

ISO 4217 currency code. Possible values include: CAD & USD. Note: as of today, currency supports a single value.

Enum: Description
USD

United States Dollar

CAD

Canadian Dollar

… 1 more
required
object
reference_id
required
string or null [ 1 .. 255 ] characters

A custom reference ID for your platform to track the object. It can be any string.

capture_at
required
integer or null <int64> >= 0
authorization_code
required
string or null

Authorization code returned from the card issuer after a credit card payment is authorized

api_version
string
auto_capture
boolean
object or null

Any custom data your platform chooses to attach to this resource. The custom data must be key-value pairs and not contain any personally identifiable information (PII) or payment card (PCI) data.

object or null
fee_amount
integer
fee_amount_refundable
integer
fee_type
string

Specifies the fee type your platform will use to collect fee from the payment.

Enum: Description
rent_surcharge

rent surcharge fee type for which collect net income and corresponding taxes for the merchant(landlord), i.e direct tax ONLY on the rent amount(amount - fee_amount)

platform_fee

platform fee type

initiated_by
string

Indicates who initiated a payment. Possible values include: customer, merchant, none.

Enum: Description
customer
merchant
… 1 more
object or null

The resource ID and path for the Order that your app created and associated with the payment.

Array of objects or null
object or null

THIS SHOULD NOT SHOW UP

object or null

THIS SHOULD NOT SHOW UP

400

INVALID_PARAMS

403

NOT_AUTHORIZED

500

UNEXPECTED_ERROR

Request samples
application/json
{
  • "custom_data": {
    • "Another Key": "some value",
    • "a_reference_number": 4
    },
  • "rbits": null,
  • "reference_id": "dfeb052b-ae8c-4a69-b909-8d9ecdd7c742"
}
Response samples
application/json
{
  • "amount": 1000,
  • "amount_refunded": 1000,
  • "amount_disputed": 1000,
  • "auto_capture": false,
  • "capture_at": null,
  • "create_time": 1510079535,
  • "currency": "USD",
  • "custom_data": {
    • "invoice_id": "54321"
    },
  • "failure_reason": null,
  • "fee_amount": 0,
  • "fee_amount_refundable": 0,
  • "id": "00000000-0000-0000-0000-00006fa82d45",
  • "order": null,
  • "owner": {
    • "id": "be2b42e5-b808-40ae-9bbe-3291ab493f57",
    • "path": "/accounts/be2b42e5-b808-40ae-9bbe-3291ab493f57",
    • "resource": "accounts"
    },
  • "path": "/payments/00000000-0000-0000-0000-00006fa82d45",
  • "payment_method": {
    • "id": "00000000-6261-5553-0000-0000000001b8",
    • "path": "/payment_methods/00000000-6261-5553-0000-0000000001b8",
    • "resource": "payment_methods"
    },
  • "pending_reasons": [
    • {
      • "details": [ ],
      • "reason_code": "PROCESSING",
      • "reason_message": "Payment is being processed."
      }
    ],
  • "resource": "payments",
  • "status": "pending",
  • "authorization_code": "0224241",
  • "txnr_app_fee": null,
  • "txnr_merchant": null,
  • "initiated_by": "none",
  • "api_version": "3.1",
  • "reference_id": "dfeb052b-ae8c-4a69-b909-8d9ecdd7c742"
}