Developer preview API v1

Sandbox only. No real funds moved. No production access is granted here. Access requirements

Protobuf v1

Plan with the published DeveloperApi service

The DeveloperApi service contract, fully-qualified routes, and compiled prost messages are real and versioned; a public gRPC transport is not production-activated until PAP-1125.

Download protobuf

DeveloperApi service contract

The v1 protobuf artifact publishes service DeveloperApi with rpc CreatePayment paired to the REST createPayment operation and rpc CreateRefund registered with status paired_not_activated. Both compile into prost messages with versioned field tags checked in CI.

Fully-qualified routes and parity

The gRPC surface uses /pap.developer.v1.DeveloperApi/CreatePayment and /pap.developer.v1.DeveloperApi/CreateRefund. Request fields mirror the REST DTOs, so a single reviewed request shape works over either transport.

Activation is explicit

gRPC DeveloperApi service contract published; not production-activated until PAP-1125. No production gRPC endpoint is available before that separate, independently recorded activation decision.

Service surface

service DeveloperApi {
  rpc CreatePayment(CreatePaymentRequestV1) returns (CreatePaymentResponseV1);
  rpc CreateRefund(CreateRefundRequestV1) returns (CreateRefundResponseV1);
}

/pap.developer.v1.DeveloperApi/CreatePayment
/pap.developer.v1.DeveloperApi/CreateRefund

Compile the reviewed messages

protoc --descriptor_set_out=pap-developer-v1.pb pap-developer-v1.proto
# gRPC DeveloperApi service contract published; not production-activated until PAP-1125.

The complete protobuf contract

pap-developer-v1.proto

A versioned service definition for your own tooling. Publishing this contract does not activate the gRPC transport.

protobuf / v1

Use the download link above to open the protobuf contract.